the StandardSession is not big, I would go back and guess it is your
application.
The key is to read the profiling data correctly, that's where I would start.
Tomcat has been optimized for memory and cpu usage, so 11MB session
objects would have been discovered early on.
John McClain wrote:
I am profiling our application in jprofiler. I have noticed that the deep
size of StandardSession object for each user is VERY large - ~ 11+mb. Yet I
know that we are not adding that much data. Where is all that memory coming
from? Is it truly non static data that is overhead for each session, or is
it static data that each session points to?
Does anyone out there have a strategy for finding memory leaks in a Tomcat
application? I am not finding ours.
John McClain
Senior Software Engineer
TCS Healthcare
[EMAIL PROTECTED]
(530)886-1700x235
"Skepticism is the first step toward truth"
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Filip Hanik
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
