Hi,
the only hint I can give in a hurry know, play arround with parameters of
the 
MRUMemoryStore component I developed. Maybe there are some leaks I didn't
determined.
- on/of filesystem store
- heapsize
- max. objects in the cache
...

Cheers
Gerhard

> Hi all, 
> 
> I'm back from the dungeons of load testing. And I don't have particularly
> good news, I'm afraid.
> 
> C2 leaks memory and CPU. The accompanying PNG shows the graphs of a
> loadtest
> with loadrunner, on tomcat 3.2.1 and C2 cvs version of last week, with 50
> concurrent users surfing around on the simple sample pages (no xsp, no
> sql,
> just the xml->html pages)
> 
> The graphs don't look good, to say the least. 
> 
> Moreover, when I stopped loadrunner, and monitored the CPU used by java,
> it
> kept burning 50-70% (even after 2 days). It was sort of cyclic behaviour:
> it
> dropped to 0%, raised to 50-70%, dropped again to 0%, and so on. I also
> saw
> the java process eating memory away (approx. 10MB/h)
> 
> The test was done with loadrunner 6.5 on a single 350 MHz cpu with 196MB
> RAM, OS: NT 4, JVM: Sun JDK1.3.1.
> 
> And now for the really bad news: I don't have a clue as how to find the
> source of such a leak. I could browse step-by-step through the code, but
> this seems a daunting task to say the least. Has anyone some hints as to
> say
> "I would begin looking there", or "I would first test this and see what
> happens", ... ? I've already been musing about the pooling of the
> components
> (probably components that aren't given back to the pool), but that is also
> pretty hard to find.
> 
> Thanks for any pointers,
> 
> tomK
> 
> 

-- 
Gerhard Fröhlich
[EMAIL PROTECTED]

"black holes are,
when GOD is dividing by zero" 

GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

loadrunner.png

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to