Nick, I doubt adding 4GB RAM would suffice for any realistic report.
In my testing we had a 12MB report that was ported to the new format and it blew up my server till we increased the Java VM memory to 2GB heap. I shudder to think what some of our larger reports would require. The current implementation is just not suitable for production use. Yegor had given some tips on how to workaround the problem using generation to XML and then swapping the file to the xlsx format after the the file was generated. I would investigate that. The thread is here<https://mail.google.com/mail/#label/POI/12288df2b983a66d> /sanjay 2009/8/3 Nick Burch <[email protected]> > On Fri, 31 Jul 2009, jayrp11 wrote: > >> We are in process of migrating from HSSF to SS model. We have already >> converted our code base to SS model and while testing encountered with >> strange issue. Memory requirement is very high in SS model also same >> degrades performance while processing 2007 excel file >> > > This has been discussed several times before, please take a look at the > list archives for details. Short summary - xml processing takes more memory > than OLE2 processing, and the xml wrapper layer we use takes more memory > again, but makes development much faster. Given that we still haven't quite > finished 3.5, quicker development is an important feature! > > If high memory use is a really big issue for you, then it's certainly > possible that you could sponsor someone to work on reducing the memory > footprint. Personally, I compared my daily programming rate with the cost of > putting another 4gb of memory into all my servers, and would've barely been > able to justify the cost of firing POI up in a profiler and poking around, > let alone trying to fix anything... > > Nick > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
