[xep-support] Re: not enough memory to format (Java heap size)

From: Gerald Wiesinger <Gerald_Wiesinger@at.ibm.com>
Date: Fri May 06 2011 - 00:07:52 PDT

hello,
there is not much of a solution that i can propose. i can only share ourexperience.
we are creating documents with 2000-3000 and some more pages whichprimarily contain tables. these require even more memory then normal textbased documents.
we are running XEP on a WebSphere server on z/OS with 64Bit mode enabledand the rendering process of our biggest documents takes up to 8GBs.
using the 2 step process: first create the XEP intermediate file format andthen do the final rendering did not change much. the major problem seems tobe the xep file in xml format to be stored completely in memory.afail, future versions of websphere allow compression of objects in memorywhich would save a lot, since xml files can usually be heavily deflated -not sure if such a "virtual memory" compression is available somewhere.
we also attempted to do a splitting of the transformed fo file intomultiples and then do rendering, but this causes unwanted page breaks atthe edges of each split document and it is hard to work with continuos pageheaders and footers (page numbering).we have been able to make it work but not in a generic way. only geared tothe majority of our documents. so we dropped this and increased the memory(in 64Bit mode) - which is quite costly on z/OS.
the same tests on a Win7 64Bit system showed the memory consumption verysimilar to what is required on the server - so once your document renderingrequires more than the possible 1.2-1.4 GB on a 32Bit system then it willbe very hard to squeeze such processes in.
_________________________________________RegardsGerald Wiesinger
IT Architect, WW CHIS and XPrint DevelopmentIBM AustriaObere Donaustrasse 95, 1020 Vienna, AustriaTel/FAX: (+43)-1-21145-6010 / 6511e-mail:gerald_wiesinger@at.ibm.com

From: Alexander Dyuzhev <dyuzhev@gmail.com>To: xep-support@renderx.comDate: 05.05.2011 21:23Subject: [xep-support] not enough memory to format (Java heap size)Sent by: xep-support-bounces@renderx.com

I have tested old build XEPWin Version 4.18 build 20100322.In file CliserService.exe.config I added string:<add key="CliserService.JavaOptions" value="-Xms512M -Xmx756M" />After that the process ended successfully.
Please note, old version have parameter name="CliserService.JavaOptions",but last version "JAVA-OPTIONS".May be new version CliserServicedon't transfer JAVA-OPTIONS to JVM ?

2011/5/5 <xep-support-request@renderx.com>

      Today's Topics:
       1. not enough memory to format (Java heap size) (Alexander Dyuzhev)

      ----------------------------------------------------------------------

      Message: 1 Date: Thu, 5 May 2011 19:57:10 +0400 From: Alexander Dyuzhev <dyuzhev@gmail.com> To: xep-support@renderx.com Subject: [xep-support] not enough memory to format (Java heap size) Message-ID: <BANLkTi=YWbQ0Enn4KRqXVFaCxgUJEwOKVw@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1"
      Hello!
      I have question concerning Java heap size setting for XEPWin. For some big xml documents (about 7Mb source .xml, and 20Mb .fo file, 500 pages) I get the error "not enough memory to format". I have edited .config file for Cliser service and set JAVA-OPTION to "-Xms512M -Xmx1024M", then restart Cliser service - the same error "not enough memory to format". After that I open Task Manager and saw that process javaw.exe is always using about only 290Mb of RAM.
      Then I tried run just XEP (not XEPWin). The process ended with error also. And memory size used by java.exe process is also about 290Mb. After that I run XEP with parameters -Xms512M -Xmx1024M in xep.bat file. The process ended successfully. BUT memory used by java.exe procces was about 690Mb.
      What do I wrong ? Why -Xms -Xmx does not affected to XEPWin ?
      My computer configuration is: 2Gb RAM, 250Gb free space on hdd, Core2Duo CPU 2.4Ghz, WinXP SP3 32bit.
      I use last version XEPWin (april 2011) and Java VM Version 6 Update 25.
      Thank you.
      Best regards, Alexander Dyuzhev

      -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.renderx.com/pipermail/xep-support/attachments/20110505/1168ed5b/attachment-0001.html >
      ------------------------------
      _______________________________________________ Xep-support mailing list Xep-support@renderx.com http://lists.renderx.com/mailman/listinfo/xep-support

      End of Xep-support Digest, Vol 8, Issue 1 *****************************************

-- ,

_______________________________________________(*) To unsubscribe, please visithttp://lists.renderx.com/mailman/options/xep-support(*) By using the Service, you expressly agree to these Terms of Servicehttp://www.renderx.com/terms-of-service.html
!DSPAM:87,4dc39e7863731543119642!

_______________________________________________(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html
Received on Fri May 6 00:08:51 2011

This archive was generated by hypermail 2.1.8 : Fri May 06 2011 - 00:09:00 PDT