What options exist for trying to reduce the memory footprint during a module install? Our workspace export is about 140Mb, and doing a first time install of Magnolia (including our module) requires about 4G of heap. I tried importing the XML export directly into a standalone JackRabbit repository, and it takes about 2.5G of heap. So, I exported various parts of our workspace, and now the largest export file is only about 7Mb in size. I can easily import all of the files and restore our workspace into a standalone JackRabbit repository in under 512Mb of heap. But the Magnolia module installation still requires about 4G of heap (anything less and I get out of memory exceptions).
So, the basic question is how would I go about reducing the memory requirement? I took a look at the module version handler, but am not sure what I would over-ride in there to try and reduce the memory requirement. My initial suspicion is that all the imports are being handled in the same session transaction leading to memory bloat. Is that what happens? Thanks in advance for any directions on how to handle this. Rakesh ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
