Re: diagnosing memory consumption and optimization
Re: diagnosing memory consumption and optimization
- Subject: Re: diagnosing memory consumption and optimization
- From: Arturo Pérez <email@hidden>
- Date: Wed, 24 Mar 2004 20:59:25 -0500
On Mar 24, 2004, at 8:05 PM, Rob Lockstone wrote:
Perhaps a third party tool like JProfiler
<http://www.ej-technologies.com/index.html> or OptimizeIt
<http://www.borland.com/optimizeit/>?
Rob
We used OptimizeIt! with great success. Our memory usage per instance
went from something like 300MB to just over 100MB. The guy doing it
took about a week (including the OptimizeIt! learning curve).
On Mar 24, 2004, at 16:45, Jonathan Rochkind wrote:
How do I tell the difference between these scenarios? If there is one
particular piece of code that's a memory hog, how do I identify it?
It's a large and complex app, so it needs to be something I can apply
to the app actually in use, actually deployed, since my attempts to
test it offline may not match the real world usage.
Any suggestions? Memory optimization or tuning is not something I
know anything about.
OptimizeIt and brethren will help you identify the culprit. The other
thing you might want to do is play with the GC tuning parameters. That
course is fraught with peril but if you have the time to experiment it
may really payoff.
http://java.sun.com/docs/hotspot/gc1.4.2/
http://www-106.ibm.com/developerworks/ibm/library/i-gctroub/
--arturo
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.