WO and Memory Management
WO and Memory Management
- Subject: WO and Memory Management
- From: Owen McKerrow <email@hidden>
- Date: Fri, 14 Jul 2006 11:15:59 +1000
Hi All,
We are setting up an application of ours on a clients server, they
did some stress testing to see if they needed a bigger box and
discovered something strange.
Their comments ....
The webobjects versions have been stress tested further, we are
getting ok
results but far worse then I was hoping. RIS Public faired worse
the RIS
with it starting to get error with only 5 simultaneous users making
simple
request 5 seconds apart (running with 2 instances each with -mx512M.
A major point of interest is that garbage collection does not
appear to be
active for these instances. We ran the tests yesterday and the
started to
consume over 500M per instance (2 instance running for RIS and
RISPublic).
This morning after no activity all night the process are still
using the
full memory set. To me this is a bit of a concern, can you guys
check your
side to see if it the same there, or if there is some configuration
options
that can be put in place to improve this?
The strange thing here is that the instances don't seem to be
releasing memory. Is this normal ? Is there a setting I need to tweak
somewhere in JavaMonitor ?
And while we are talking abou memory, can someone refresh my memory
( no pun intended ), but its better to explicitly call System.gc() in
WO App's. Whats the rule of thumb here in terms of how often, is
there a better spot than others etc etc ?
Thanks again
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - -
"I like the way this project has somehow, against all common sense,
got itself made."
- Peter Jackson, "The Lord of The Rings"
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden