Hello Kirill, Nor am I a regular reader of this list, neither I am a regular POI committer - but from time to time, I fix bugs that I encounter. Nevertheless, I think I can share some advice on how to get help with your issue:
1. Put some effort in it before asking on the list: if you think memory consumption has increased significantly, create a test case that is easy to reproduce. It should be possible to demonstrate the bug with much less memory, i.e. when run with -Xmx512m. Not everyone has a machine with 10+ GB RAM at hand, just to test your code. 2. If you you have done that, investigate. Create heap dumps with both versions and look for differences. This should not be too difficult - your signature says “Senior Software Engineer”, that implies you know how to use a debugger. If not, think about changing your job title. 3. Create a bug report. Include a small, simple, compilable program that demonstrates the bug. Include your demonstration program (source) and all your observations from step 2 in the report. Don’t link to external sites like google drive unless absolutely necessary. 4. I assume you get paid for supporting your company’s product. People working on POI mostly are unpaid volunteers. So don’t expect others to do your work - create nice bug reports, respond to questions, try to fix the bug yourself. 5. If you can’t fix the bug yourself, it is absolutely critical for your company to get it fixed, and there’s no progress to be seen in the issue tracker, hire a freelance developer to fix it for you. Ok, hope that gets you started. Axel On 2019/07/08 09:37:08, Kirill Rajbhandary <[email protected]> wrote: > Dear POI DEV Team,> > > Do you have any updates regarding to the below described issue?> > > Best regards,> > Kirill Rajbhandary> > > > Senior Software Engineer> > Jedox AG> > > > www.jedox.com> > Kirill Rajbhandary> > Senior Software Engineer> > +49 761 15147 237> > Jedox AG> > Bismarckallee 7a> > 79098Freiburg im Breisgau> > Germany> > Executive Board: Florian Winterstein (Chairman), Bernd Eisenblätter, > Maximilian Prinz zu Hohenlohe-Waldenburg> > Supervisory Board: Bernhard Wöbker (Chairman), Curt Gunsenheimer, Thilo > Schmid> > Place of Business: Amtsgericht Freiburg HRB 702118> > > > [TM.V06112018]> > From: Kirill Rajbhandary <[email protected]> > > Sent: Thursday, 13 June, 2019 16:39> > To: [email protected]> > Subject: POI memory usage degradation> > > Dear POI DEV Team,> > > Unfortunately, I found out that the latest POI library poi-ooxml with > versions 4.0.1, 4.1.0 consumes much more memory than the version 3.17 when it > is required to write information to already existing large Excel file.> > It requires approximately 6GB Java Heap Space to add these rows using > poi-ooxml library with version 3.17 but it is not enough even twice more > (12GB) with version 4.0.1 or 4.1.0. Besides, the performance is much worse > with the latest versions of poi-ooxml. OpenJDK 11.0.02 was used to run this > example.> > In attachment the corresponding example with ExcelWriter class can be found > that tries to add only 5 rows to already existing sheet "Sheet2" having only > header row with 16 columns. The first sheet "Sheet1" of this file already > contains 240K rows with 23 columns. Zipped ExcelWriter with > Test-Template.xslx can be downloaded from the next link:> > > https://drive.google.com/file/d/1vq6WvMv5mSFUzyJinN9aoYRBStxZuJCq/view> > > To run ExcelWriter main method, please specify the full path to > Test-Template.xlsx and result file path. To change poi-ooxml version, it > requires to change it in pom.xml, rebuild the project and run it again.> > > Could you please advise why it became worse comparing with the old library > version poi-ooxml-3.17.jar and how it could be improved?> > > Best regards,> > Kirill Rajbhandary> > > Senior Software Engineer > > Jedox AG> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
