This really sounds like something specific to your setup, either your
app or your profile (are you holding onto page references somewhere?).
I have an app with 10-20 pages that has run with no memory issues for
months on end, running with 512Mb max memory. Any memory issues in
the app have been mine, dealing a couple of tables that have upwards
of a million records each. Definitely not seeing anything like what
you describe.
Robert
On Mar 17, 2009, at 3/179:59 AM , Yuri Ushakov wrote:
Hello.
I'm using Tapestry 5.0.18. I've been doing a load test using 10
concurrent
users (never more than 10 parallel requests). I've set up page pool
to 10
pages also. I checked it - if 11th user comes, there is the tapestry
exception about hard-limit. So, the Tomcat is run with -Xmx2048M.
The ten
users were browsing 4 particular pages for about 40 - 50 minutes.
They are
quite ordinary pages, some small, one big (kinda user dashboard).
What I get is constant 85% heap usage with:
196 instances of PageImpl
308277 instances of ComponentPageElementImpl
Here is the profiler screenshot:
http://img19.imageshack.us/img19/6170/tapestrymemory.png
Questions are:
1. Why there is about 1G of retained CPEI objects.
2. Why there are 196 PageImpl objects, with page pool set to 10, and
only 4
pages in use.
3. Where can I look for any clues? Enable some tapestry debugging?
Read some
important document explaining this situation?
Thanks for any help.
Yuri.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
