Convert from PDF to PDF/A 3B takes forever and it takes as much as 9GB of Memory!

we have purchased Aspose.Total for .NET

we are trying to convert a 50MB Excel file to PDF/A 3B, and this is what we did

Load Excel to workbook - 3secs
Convert tor PDF - 14 Mins !! ~2.4 GB Memory usage
then Convert to PDF/A 3B - Forever !!!!! > 9GB Memory usage

Aspose Cell doesn't support direct conversion to PDF/A 3B only up to 1B i think



please advise

H/W
Core i7 2.8 Ghz
32GB
SSD

Hi Eric,


Thanks for contacting support.

Can you please share the input Excel file, so that we can test the scenario in our environment. We are sorry for this inconvenience.

trying to upload but failed, source code + sample file = ~70Mb


please advise

screenshots attached

Hi Eric,


Our forums support uploading a document maximum of 25MB. However in order to share large documents, you may consider uploading it to some free file sharer and share the link with us.

excel file attached

Hi Eric,


Thank you for sharing a source Excel file. We’re investigating it and will get back to you soon.

Hi Eric,


Thank you for sharing a problematic Excel file. We managed to replicate the problem of time and memory consumption using Aspose.Cells API. It has been logged under ticket id CELLSNET-44653 in our bug tracking system. We’ll let you know once a significant progress has been made in this regard. We’re sorry for the inconvenience caused. We’re investigating Aspose.Pdf API part and will share its ticket id later in this forum thread.

Hi Eric,


Thank you for being patient. In reference to the ticket id CELLSNET-44653, we have investigated further and come to the conclusion that Aspose.Cells API is not inefficient in converting your Excel file to PDF. There are a lot of pages (2,500) in each worksheet of this Excel. In such scenarios, we don’t recommend to set OnePagePerSheet to true. This process will consume a lot of memory to process large amount of the content (20000 pages). The OnePagePerSheet option is fruitful in cases to process few pages per sheet (e.g. 5 to 10). Please set OnePagePerSheet to false. The memory cost will go down.

Note: we have closed ticket id CELLSNET-44653 with “Won’t Fix” status.

Hi,


The main problem for this is not the conversion between Excel to PDF, we understand that it took as much as 2.5GB memory to do so with the sample excel and it took around 14mins , that seems acceptable,

The problem is when we do the following:

pdfDoc.Convert(“log.xml”, PdfFormat.PDF_A_3B, ConvertErrorAction.Delete);
right after we have converted the excel to PDF, using the pdf stream to convert to PDF/A -3B


this uses >10GB of memory and took ~2h 16m and some cases it crashed.

please do let us know if this is normal for aspose API.

meanwhile we will try your suggestion as well.

Thanks,

Hi Eric,


Thanks for sharing the details.

I have tested the scenario of PDF to PDF/A_3b conversion using Aspose.Pdf for .NET 11.9.0 and as per my observations, the conversion process hikes CPU usage to 81% and Memory consumption increased by 1.6GB. For the sake of resolution, I have logged it as PDFNET-41273 in our issue tracking system. We will further look into the details of this problem and will keep you updated on the status of correction. Please be patient and spare us little time. We are sorry for this inconvenience.

BTW, just a note, the reason you only get max 1.6GB memory usage probably due to the fact that the app is running in 32bit mode (any cpu), try change it to 64bit mode you will see it consume all available memory it can get on the machine.

Hi Eric,

grjes:
BTW, just a note, the reason you only get max 1.6GB memory usage probably due to the fact that the app is running in 32bit mode (any cpu), try change it to 64bit mode you will see it consume all available memory it can get on the machine.

Thanks for sharing your findings. Our product team will consider it while investigating the issue. We will notify you as soon as we made some significant progress towards issue resolution.

We are sorry for the inconvenience.

Best Regards,

Any update so far?

Hi Eric,


Thanks for your inquriy. We have recently noticed your reported issue and it is still pending for investigation in the queue, with other issues. We will notify you as soon as we made some significant progress towards issue resolution.

We are sorry for the inconvenience.

Best Regards,

any update yet?

Hi Eric,


Thanks for your inquiry. Your above reported issue is still not fixed. It is pending for investigation, as product team is busy in resolving other issues in the queue. We will notify you, as soon as we made some significant progress towards issue resolution.

Thanks for your patience and cooperation.

Best Regards,

Hi Eric,


Thanks for your inquriy. I am afraid issue is still pending for investigation in the queue. However, we have requested our product team to investigate and share an ETA/update at their earliest. We will update you as soon as we get a feedback.

Thanks for your patience and cooperation.

Best Regards,

is there any progress or updates regarding this issue?

Hi Eric,


Thanks for your inquriy. We have made some fixes in the API and it reduced execution time to 1h 40 min. The fix will be available in upcoming release i.e. Aspose.Pdf for .NET 16.11.0. However, please note Adobe Acrobat Preflight hangs forever for conversion. We will appreciate it if you please confirm your acceptable conversion time.

We are sorry for the inconvenience.

Best Regards,