If you
set the gc debug flags (dependent on JVM) you can get gc to log gc runs to
file (or output) and easily cross this one off the list of
possibilities.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 24 June 2003 12:13
To: [EMAIL PROTECTED]
Subject: Antwort: RE: [JBoss-dev] performance drop
Thanks for the link , but GC was just meant as illustration :-) In fact I think that most probably another JBoss internal background process is causing this drop
"Healey, Alex" <[EMAIL PROTECTED]>
Gesendet von: [EMAIL PROTECTED]24.06.2003 12:57
Bitte antworten an jboss-development
An: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Kopie:
Thema: RE: [JBoss-dev] performance drop
Have a look at this article if you want to investigate gc performance.
http://developer.java.sun.com/developer/technicalArticles/Programming/turbo/
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 24 June 2003 11:47
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] performance drop
When running a grinder entity bean loadtest against JBoss-3.2.2RC2 we realize a significant performance drop ever 60 seconds for 2-5 seconds. Obviously there is some periodic background processing. Has anybody an idea what kind of process is causing this drop ( garbage collector ? )
Regards
Ulf
----------------------------------------------------------------------
If you have received this e-mail in error or wish to read our e-mail
disclaimer statement and monitoring policy, please refer to
http://www.drkw.com/disc/email/ or contact the sender.
----------------------------------------------------------------------
----------------------------------------------------------------------
If you have received this e-mail in error or wish to read our e-mail
disclaimer statement and monitoring policy, please refer to
http://www.drkw.com/disc/email/ or contact the sender.
----------------------------------------------------------------------
