Frank,
keep in mind apps that sit on 32bit os can only grab just under 2 anyway. I
would  test your -xms and -xmx at 1400 in the jrun.config. We ran multiple
32bit prod servers at this successfully at my last company. Also
consider *+AggressiveHeap
switch.*

Also revisit your CF settings in general -- and after reviewing all, if its
still giving you a headache, you might consider devoting a separate box
either virtual or physical, to do your large pdf creation if you are indeed
getting slammed with requests and the process is affecting general app
performance.

Get fusion-reactor in there to, if you don't already -- to help you monitor.

-Steve


On Tue, Sep 14, 2010 at 12:25 PM, Frank Moorman <[email protected]
> wrote:

> Does anyone know what the maximum java heap size is for CF9?  I remember
> that CF7 would not start whenever it was set above 1024MB.  (32-bit windows
> environment)
>
> Our server is set to 1024MB right now and we are encountering out of memory
> errors in Java when creating large PDFs. (Lots of images)  We are looking at
> increasing the physical memory on the server from 2GB to 4GB.  (Which thanks
> to windows memory management will probably give us a gain of 1GB) Once we
> have more memory we will increase the Java Heap size appropriately.
>
> This is only a stopgap move. We know that the number of images is affecting
> the memory usage. The PDFs are crashing right now when they include
> approximately 60 photos. The long term plan is to create the pdfs one page
> at a time (with no more than 14 images each) and then use the CFPDF command
> to merge the pages into one file.
>
> Thanks,
> Frank
>
>
> -------------------------------------------------------------
> To unsubscribe from this list, manage your profile @
> http://www.acfug.org?fa=login.edituserform
>
> For more info, see http://www.acfug.org/mailinglists
> Archive @ http://www.mail-archive.com/discussion%40acfug.org/
> List hosted by http://www.fusionlink.com
> -------------------------------------------------------------
>
>
>
>

Reply via email to