my company is currently using a competitors component. however this component takes several minutes to load a 197 page reports, and more worryingly, it uses a 250 - 300meg of memory throughout this document generation process. i queried this and was told that PDF creation was expensive and basically there was no fix. so if multiple users request a PDF concurrently I will have to create a queue to prevent overload!!
so i am looking around at different components now. so can anyone comment on whether ASPOSE PDF is more efficient than what i have described for a large report created via a Stream? if so ill set up a trial app and give it a whirl.
Aspose.Pdf has better performance and small Memory usage but that is correlative to what report you want to generate. Please use our trial apps for good experiences.
Aspose.Pdf provides 2 working mode. One is the normal working mode, using much memory but provide more flexibility. The other mode is described in http://www.aspose.com/wiki/default.aspx/Aspose.Pdf/WritingPdfFileDirectly.html. It use less memory but some of the advanced features are not supported.
the 197 page report that I am using as my example, will contain rows and column headers as I will be using a .NET dataTable as the data source. I will be streaming the PDF straight to the browser. will this be possible using your WritingPdfFileDirectly method?
It is possible. But in WritingPdfFileDirectly mode, large table has low performance. If you can split a large table into small tables, it will be better.