cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Langham" <mlang...@sundn.de>
Subject AW: [C2] Loadtest
Date Mon, 20 Aug 2001 15:02:31 GMT
We have been using JProbe to find the source of memory leaks (the last time
being the sub-sitemap problem a couple of weeks back). JProble allows you to
snapshot the memory and then you can find out which objects remain in memory
after the request has been processed.

So that may be a start in narrowing down where the leaks are coming from.

Matthew

--
Open Source Group               sunShine - Lighting up e:Business
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel: +49-5251-1581-30   [mlangham@sundn.de - http://www.sundn.de]
=================================================================


-----Ursprüngliche Nachricht-----
Von: tom.klaasen@the-ecorp.com [mailto:tom.klaasen@the-ecorp.com]
Gesendet: Montag, 20. August 2001 16:50
An: cocoon-dev@xml.apache.org
Betreff: [C2] Loadtest


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



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message