wow 10,000 client threads in parallel!!!!
 
geeeeezus... and do you run that from teh same box?
 
glad you can't bring JBOSS down to it's knees... hehe... (also please turn off HTML when posting to this list)
 
You might want to try turning OFF the cache  completely (by specifying the nopassivation cache in the standardjboss.xml stuff).
 
Also keep in mind that if you are retrieving 1250 records then we need to serialize 1250 proxies which should take 100 times more than 12,5 proxies :) so if you see 1000 millisecond (e.g. a second :) with the cache turned OFF then you really have a large query being returned.
 
Other than that, just very proud that you can't crash our stuff (your stuff now vinay ;-)... what is the VM on Tru64?
 
marc
 
 
 
 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of K.V. Vinay Menon
Sent: Monday, June 04, 2001 7:07 AM
To: User @ JBoss; Dev @ JBoss
Subject: [JBoss-dev] Logging Cache Hits

Hi,
     Does anyone know how to turn on cache hit tracking in JBoss without recompiling the code!? Is this possible? I am trying to stress JBoss to about as far as it can get [it has not yet fallen over!!! ] but the time for queries seem a bit odd. I have large intial retrieval times and then they fall off [as expected I guess dues to cache hits - want to confirm this though]. But I do get spikes in the middle [probably because the number of beans has reached a stage where passivation kicks in]. What I'd like to know is whether successive queries actually hit the database or work [as promised] by hitting the cache even under very high loads. I am testing with about 10000 client threads hitting the application server any where between 10milliseconds to about 1000 milliseconds on a huge Tru64 box. The queries could return 1,15,150,1250 records depending on the type of client. The underlying table has about half a million records and is an Oracle 8i database.
 
Regards,
 
Vinay

Reply via email to