Client side excel export and large memory allocation

Client side excel export and large memory allocation

Posted by: alessandrop on 8 September 2017, 10:09 am EST

• 

  alessandrop

  • Post Options:
  • Link
    Copy

  Posted 8 September 2017, 10:09 am EST

  Hi,
  
  I’ve noted that exporting a spreadsheet with thousands of rows the memory allocation grows up to the javascript heap limit and the process crash.
  
  For example, a spreadsheet with 50k rows and 30 columns (and some columns formatting) allocates initially about 290 Mb in Chrome 64 bit.
  
  Invoking the Save method of GC.Spread.Excel.IO the memory rises to more than 2 Gb and the operation fails.

  Why the export operation is so memory hungry?
  
  Is there an alternative to export to excel avoiding the issue ?
  
  This problem limits drastically the potential of the tool.

  Thanks
  
  Alessandro

• 

  deepaksharma14

  • Post Options:
  • Link
    Copy

  Posted 8 September 2017, 10:09 am EST

  Hi Alessandro,

  We have made some performance enhancement for exporting and importing in our interim build. Please download it from here and test:
  
  https://cdn.grapecity.com/devchannel/SpreadJS.Evaluation.10.1.3.zip

  Thanks,
  
  Deepak Sharma

• 

  alessandrop

  • Post Options:
  • Link
    Copy

  Posted 8 September 2017, 10:09 am EST

  Hi Deepak,
  
  I’ve tested the build but in my scenario the memory allocation continues to rise to 2Gb.

  In the attached zip file there’s a test page to reproduce the issue.
  
  How it works: choose “Template.xlsx” file, import, add 70000 rows, export.
  
  The export should fails.
  
  However, with 50000 rows it works, despite they allocates 2Gb of memory.

  Thanks
  
  Alessandro
  
  2017/06/excel-io-test.zip

• 

  deepaksharma14

  • Post Options:
  • Link
    Copy

  Posted 8 September 2017, 10:09 am EST

  Hello,

  Thank you for providing me the sample application.
  
  I am able to replicate this issue and reported it to the development as a bug. The tracking id for this issue is 238111.
  
  I will let you know as soon as I hear anything on this.

  Thanks,
  
  Deepak Sharma

• 

  alessandro.passarotto

  • Post Options:
  • Link
    Copy

  Posted 8 November 2017, 10:26 am EST

  Hi Deepak,
  
  have you any news about the issue ?

  Thanks a lot
  
  Alessandro

• 

  deepak.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 11 December 2017, 4:21 am EST

  Hi Alessandro,

  This issue is still with the development team. I have asked the development team for an update on this issue. I will let you know as soon as I get one.

  Thanks,
  
  Deepak Sharma

• 

  deepak.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 15 December 2017, 4:28 am EST

  Hello,

  Our development team suggest to use Server side export feature with Spread.Services. The major reason for this export issue is caused by memory limitation in client side which don’t have on the server side.

  Thanks,
  
  Deepak Sharma