We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

PNG generation is VERY slow

Hi,

We have a specific PDF - RBCCodeOfConduct.pdf - that when we open with Aspose and just generate a PNG of the first page takes over 90 seconds! Actually, with 18.7.0 it took over 90 seconds. I just downloaded the latest release (19.3) and it now takes 115 seconds.We’ve tried with other “similar” files and their performance is much quicker, although across the board the timings are slower between releases…

I’ve attached sample code and also an Excel file with runs for the included PDF files and the two releases to show the differences.

Is there anything that can be done to improve the performance on our file? Is there something wrong or different with the content of the PDF that could be changed to make it convert quicker? Why is the new release slower, across the board???

Thanks,
Andy.

PDFTestingAndReport.7.zip (3.1 MB)

@bsant

Thanks for contacting support.

We were able to replicate the issue that you have mentioned in your post while testing the scenario using Aspose.PDF for .NET 19.3. For the sake of detailed investigation, we have logged it as PDFNET-46221 in our issue tracking system. We will further investigate the reasons behind this issue and keep you posted with the status of its correction. Please be patient and spare us little time.

We are sorry for the inconvenience.

Just checking to see if there has been any progress on this issue? I’ve heard nothing and our customer wants an update on the status!

Thanks,
Andy

@bsant

We regret to share that your issue has not been yet resolved due to low priority and other issues in the queue. Please note that issues under free support model are resolved on first come first serve basis unlike our priority support where they are dealt with high precedence on urgent basis. We will surely let you know as soon as we have some definite updates regarding issue resolution. Please spare us little time.

We are sorry for the inconvenience.

Hi,

Any update on this? It’s still an issue, as far as we can tell. Is this bug going to be fixed?

Thanks,
Andy.

@bsant

Regretfully the ticket is not yet resolved as it needs more time to get fully investigated and resolved. We will surely take care of your concerns during investigation of this issue and let you know as soon as it is resolved. Please spare us some time.

We are sorry for the inconvenience.