I am watching in task manager when I do a workbook.open and some processing my worker process goes up to 100 Meg, I even tried setting workbook = nothing but now it still shows 100 Meg and my next subsequent process it just increases from there.
Hi,
Thanks for your inquiry.
Well, Aspose.Cells is a pure .Net component and we totally rely on .NET Garbage Collector(GC) to release memory. GC won't release memory when you set the objects to nothing. It only releases memory when it thinks it's appropriate, Also in web asp.net application, memory collection is not only handled by GC, but also by internal asp.net process. Moreover, normally, if you open a 10MB file, you will need approx. 100MB memory to process the file. So, I think you don't need to afraid of it, it's just a routine of IIS in an asp.net application.
Thank you.
After much testing last evening we found that myself and another developer were looping through an excel file 23 Meg file each sheet opening and looping through the max data rows which is about 200 rows. On both our IIS 7.0 machines we were able to do it without an issue. On three IIS 6.0 boxes after it got through 20 sheets out of 24, the application just hung up and IIS was crashed. The worker process was pinged at 153 Meg but even though the worker process did not look like it had maxed out by any means the application memory just completly froze and we had to reset IIS every single time on these IIS 6.0 machines.
Actually IIS doesn't free the memory as soon as it isn't used. IIS preserves it for performance consideration. However, from your test case, I think IIS6.0 don't free the memory very efficiently for large memory programs.
Can you post your newest code here? We will check if there are any change to optimize your code for memory usage. Thank you.
Hi,
And for your further reference, please check the doc: `http://technet.microsoft.com/en-us/library/cc786196.aspx`
Thank you.