europe72 Posted November 3, 2009 Share Posted November 3, 2009 It appears as though when the ignore pagination property for a report is checked that virtualization does not work - meaning swapfiles are 0KB, regular virt files are not written at all, and gzip appears to do nothing. I can certainly see how this would be the case, but am looking for confirmation. Thanks a lot. Link to comment Share on other sites More sharing options...
lucianc Posted December 3, 2009 Share Posted December 3, 2009 That's how it currently works indeed. Virtualization uses report pages as externalizable object, and when you have a single page no virtualization occurs.Log a feature request to address this limitation.Regards,Lucian Link to comment Share on other sites More sharing options...
europe72 Posted February 24, 2010 Author Share Posted February 24, 2010 0004594 Case submitted and assigned to you. Thanks Link to comment Share on other sites More sharing options...
arnljot Posted March 5, 2010 Share Posted March 5, 2010 This is something I'd vote for. Excel and webreports are prefered without pagination here, but with missing virtualization we're running into heap problems. Link to comment Share on other sites More sharing options...
vostapenko Posted February 4, 2011 Share Posted February 4, 2011 Is there any workaround for this? Link to comment Share on other sites More sharing options...
europe72 Posted February 5, 2011 Author Share Posted February 5, 2011 I'd also be interested if there are any good workarounds. The heap issues with Excel output are a huge problem for me. I use POI; can't use JExcel/JExcel's tmp file during write option (which is the only mem mgmt I have found for non-paginated output with an excel lib).I'm considering an investment in aspose.cells. I just can't get memory under control in non-paginated, non-virtualized excel any other way. Link to comment Share on other sites More sharing options...
vostapenko Posted February 7, 2011 Share Posted February 7, 2011 I don't know, what's JExcel tmp file, but from my point of view it doesn't correspond to the problem at all. Heap is getting full while filling the report, not while exporting. So Jexcel does not start to play its role. I'm now trying to implement postprocessing of generated paginated excel file to merge pages into one. Not sure wheather it's a good idea or not. Link to comment Share on other sites More sharing options...
europe72 Posted February 7, 2011 Author Share Posted February 7, 2011 "but from my point of view it doesn't correspond to the problem at all. Heap is getting full while filling the report, not while exporting"In the context of this thread you are absolutely correct, however the xls libs themselves have their own problems with memory. But perhaps it doesn't pay to muddy up this thread with those issues (as they are already addressed elsewhere).Anyhow, a way to use a virtualizer on a report where ignore pagination bit is flipped to true will hopefully trickle into the codebase at some point in the future. Link to comment Share on other sites More sharing options...
teodord Posted February 14, 2011 Share Posted February 14, 2011 Hi, We'll try increase priority of the mentioned tracker about virtualization of non-paginated reports. Thanks,Teodor Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now