C1.C1Excel.C1XLBook.Save latency when saved to network location

C1.C1Excel.C1XLBook.Save latency when saved to network location

Posted by: eswar.darsi on 27 October 2021, 6:25 am EST

• 

  eswar.darsi

  • Post Options:
  • Link
    Copy

  Posted 27 October 2021, 6:25 am EST

  One of our customer facing latency issue when the method C1XLBook.Save(location) is invoked where the “location” is a network path.

  We populate C1.C1Excel.C1XLBook object and call the Save method.
  
  Just want to know, how the file is created from C1 side.

  • Is the file created in a temporary location and then copied to specified location?
  • Is the file directly created in specified location? In this case, how the data is pushed to the file?
  • Does C1 restrict data transmission rate?

  Any handful document on Save mechanism is appreciated.

  Thanks,
  
  Eswar

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 28 October 2021, 4:46 am EST

  Hi,

  I know similar performance issues when saving a C1FlexGrid to a file.

  A workaround is to save the C1XLBook to a System.IO.MemoryStream and then write this stream to the network file. Here you can use a larger buffer size.
  
  Or (if the file is too large) you save the C1XLBook to a temporary file and copy this file to the network location.

  Hope this helps

  Wolfgang

• 

  avnish.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 28 October 2021, 6:40 am EST

  Hi,

  We have escalated this to the development team and will let you know when we have an update.

  [Internal Tracking ID : C1WIN-26002]

  Regards
  
  Avnish

• 

  avnish.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 3 November 2021, 2:03 am EST

  Hi,

  As per the dev team, It is a limitation. For reading and writing xls-files (BIFF8 format), C1Excel uses OLE storage objects of the Windows system and it is a known issue of OLE storage objects working slow when using a network location.

  Regards
  
  Avnish