In our application, RAM consumption is seriously spiking. Part of the problem is that one library operates on byte[] and the other uses streams (Aspose.Cells). We are paying a penalty for the in-memory conversion.
Would you be willing to add an additional method to Aspose.Cells.Workbook that has the following signature?
public void Save(byte[ ] byteArray, FileFormatType fileFormatType);
That’s what I am currently doing. I am trying to avoid the MemoryStream->byte[] conversion when trying to send the in-memory representation of the Excel document to another library. This other library transparently saves the data to a network share without my having to consider any network authentication issues, or even know exactly what share it is saved to.
We are manipulating 50 Mb Excel files (worst case) and have seen "out of memory" errors on machines with 1 Gb total available physical RAM. The "out of memory" occurs on the Save operation. Aside from other options that we can pursue, I was expecting that avoiding the data-type transformation step would help.
I understand that this is not an Aspose problem. We were hoping that an additional API would help alleviate our RAM issues.
2. Which file format do you specify when you call Workbook.Save method?
3. It seems that a font is not installed in your server. Could you please send your file created on xp development machine to nanjing@aspose.com? Thank you.