Let me first explain how we are using the Aspose.Pdf product. We have written a wrapper which uses generic tables, columns and rows to create a document. once these tables are built (and filled) we convert them into Aspose tables and generate a pdf document.
This setup is fairly succesfull until we began testing with creating documents with larger tables and started noticing the memory usage. When we start the process of converting out generic tables to aspose tables the used memory frankly explodes! (up in the 800Mb - 1GB range), of course this forces the computer to swap memory to the hard drive which grinds the whole process to a halt.
We have tried to use the Direct-To-File mode but although memory usage stays around 400 Mb(!) this is way to slow.
At the moment creating a simple document with a table with 7000 rows takes about 7-8 minutes (memory usage 500-700Mb) but anything above 10000 rows grinds to a halt due to the memory requirements.
To me these amounts of memory usage seem abnormal, can aspose explain why so much memory is consumed? and if this is expected behaviour? and what is the best way to use Aspose.Pdf if you need to make a document with a table of 90000 or more rows?