Albert R. wrote:
Can I ask you guys what kind of JVM memory settings you guys use for
those kind of setups?
We’re using WebSphere’s defaults, except for heap size. It looks like
these are the JVM memory-related args:
We’re using the default permgen size, and haven’t had any issues (so
far; we’re about 2 months into our live deployment).
On Tue, Aug 5, 2008 at 1:14 AM, AD [email protected] wrote:
so 256 Mb - 1Gb per runtime is a good estimation ? Thats higher than i
For our application, 250 MB - 1 GB was appropriate. A warmed up jruby
with rails in it seemed to sit around 50 - 100 MB, IIRC. The 1 GB case
was if a PHB clicked the “download all locations” link, which would load
about 40,000 active record objects and generate a CSV with about 40,000
rows x 15 columns. (Like I said, if we had gotten response streaming to
work, this memory requirement would have gone down dramatically.) We had
a daily job that used a pretty variable amount of memory, depending on
the amount of traffic the site had received in the previous 24-hours.
Worst-case estimates for that were around 1 GB as well.
Also, the application was written by us for another company, and is
being hosted by a third company on a different continent, so stability
(i.e. avoiding OutOfMemoryExceptions) was an /extremely/ important
factor in sizing the application. If we were hosting it, we probably
would have used 8 runtimes rather than 6.
thought. I am on 64 bit Linux with 8Gb or ram so was gonna dedicate 6Gb of
We’re running on 64-bit linux with 8GB ram as well, but we’re stuck
using WebSphere with a 32-bit JVM, so we can only use about 2 GB for the
RAM to the heap and use somewhere between 8-16 runtimes after some
discussion here. based on your estimates it seems like 6 runtimes is as
big as I would want to go without upping the RAM.
It depends on your application. If you’re not ever trying to load your
entire database into memory, 8 - 16 is probably appropriate.
To unsubscribe from this list, please visit: