I can confirm, the processing time also skyrockets on our end.
We’re also using a secondary processing pipeline to process these documents which I’ve not mentioned as of yet, as I was still trying to build an other PoC console app for this one. With that pipeline, we’ve managed to generate a 214MB PDF file using the same Original_Data2.xlsx document and almost no editing - which took even longer. If I manage to reproduce this behavior in an other PoC, I’ll make sure to let you know.
Thanks for your confirmation on it. We will also address it.
Sure, please take your time to create a console demo app with resource files as PoC and post us. We will look into it as well.
Fyi:
After careful consideration, I won’t bother you with investigating the other processing pipeline as it is not remotely practical to convert the previously mentioned (roughly 57 x 3300 cells) worksheet into a Word document [neither by recreating the table in Word nor by using the Aspose.Cells.Workbook.Save(*, SaveFormat.Docx)] and then converting the Word document to a PDF file.
Just for reference, converting the Excel to Word doesn’t take long (probably a few seconds) and increases the file size from ~2MB to ~3.6MB, whereas saving this intermediate Word document as a PDF takes roughly 15 minutes and increases the file size to 228MB, which is more than 100 fold the original Excel file size.
Do you use Aspose.Words for converting Word documents to PDF? If yes, you may post/share your issue along with resource files in the Aspose.Words forum: Aspose.Words Forum.
Yes, we do.
But I don’t think the use-case is of practical relevance as it is infeasible to display 57 columns of a Word table on a single page’s width without squashing the columns so hard, that you’re unable to read anything.
That’s why we will refrain from filing this issue - unless you specifically want to analyze the performance on a completely “broken” Word document.
You’re absolutely right; trying to fit 57 columns on a single page would make the data too small to read clearly. However, the time cost (e.g., 15 minutes) still seems excessive, and the file size (228MB) is quite large. I would suggest posting the issue along with a sample app, including the necessary resource files.
I’ll try to isolate the issue and, if possible, make sure to post it in the Aspose.Words forum.
Thank you for your efforts. If you encounter any other issue(s) or have questions regarding Aspose.Cells APIs, please don’t hesitate to reach out to us.
Just in case you want to follow the respective Word to PDF issue: Gigantic file size when saving Aspose.Words.Document as PDF
@M.Heinz
Thank you for your feedback. We have created the relevant issue CELLSNET-58078 for Cells product. We will notify you promptly once there are any updates.
Thanks @John.He ,
your colleague has already pointed that one out. I’ve been talking to them about an additional Aspose.Words issue though, which at first I didn’t want to file due to the structure/relevance of the test data, but they were interested in the report anyways. C.f. Gigantic file size when saving Aspose.Cells.Workbook as PDF - #8 by amjad.sahi.
Thank you for your additional feedback.
I think it is good that you’ve raised the Word-to-PDF performance and size issue in the Aspose.Words forum. Kindly allow the Aspose.Words team some time to thoroughly evaluate the matter. They will respond to you in the thread with their findings and further details.
No worries there. As stated earlier: For this specific document, the result is impractical to view in Word anyways, so I’m not too concerned about any immediate resolution of the Words issue.
If they’re able to improve the performance of the Aspose.Words component using the specified testcase though, I’m not against it by all means 
.
Alright and sure, let Aspose.Words team gets back to you with their analysis and findings. In the meantime, we will continue addressing the issue (i.e., CELLSNET-58078 - Gigantic file size when saving Aspose.Cells.Workbook as PDF). Rest assured, we will update you here as soon as we have new updates or make any progress to share.
This is to inform you that your issue (Ticket ID: “CELLSNET-58078”) has been resolved. The fix/enhancement will be included in the next release (Aspose.Cells v25.4) scheduled for release in the first half of April 2025. You will be notified when the next version is released.
The issues you have found earlier (filed as CELLSNET-58078) have been fixed in this update. This message was posted using Bugs notification tool by leoluo
Hi, any chance CELLSNET-58078 will be ported to Aspose cell for Java ?
We are also encountering xlsx files exported to PDF by Aspose resulted in very large PDF sizes.
Generally, we port enhancements/fixes from .NET to Java with every release to make Aspose.Cells for Java more robust and up-to-date. Could you please try the latest Aspose.Cells for Java 25.4 and let us know your feedback.
hi @amjad.sahi
just tried java 25.4 library. Still experiencing large xlsx converted to PDF in Java.
(140kb xlsx gets converted to 47MB pdf )
Also checked the release note Aspose.Cells for Java 25.4 Release Notes
and there’s no mention of gigantic file conversion fix as in the .net release.
Where can we submit the xlsx file for the dev team to take a look (for Java )
Thanks
It seems you are using different Excel files for the conversion. Anyways, we recommend you to kindly post a new thread/topic in Aspose.Cells category with all the details, sample code and resource files (please zip them prior attaching). We will then check your issue with Aspose.Cells for Java and assist you accordingly in your thread.