: Is JCS slow ?
Running the same test as standalone in a main :
Avant le test
Tue Jan 20 18:47:30 EST 2004
Tue Jan 20 18:47:30 EST 2004
Tue Jan 20 18:47:30 EST 2004
Apres le test
:((( Now it's sure, it come from JBoss, but why and where
.
Does anyone know what can enabled the debug mode ? Or if it is
possible to
force the debug mode to false ?
Thanks.
JMS.
-Original Message-
From: Spaggiari, Jean-Marc [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 20, 2004 6:51 PM
To: '[EMAIL PROTECTED]'
Subject: Re: Is JCS slow
No, no one has ever asked if JCS is slow. Something is definitely
wrong. The cache is not significantly slower than a hashtable. Can you
give more details about your configuration (i.e. the cache.ccf file) and
what you are caching.
-Original Message-
From: Spaggiari, Jean-Marc
PM
To: Turbine JCS Users List
Subject: Re: Is JCS slow ?
It looks like your memory caches are bounded at 1000 items (MaxObjects
= 1000). Thus if you put 1600 items in the cache, and then look for any
of the first 600 items, the cache will need to read them from disk,
which takes time
'
Subject: RE: Is JCS slow ?
I'm not sure what is going on. Are you getting any errors in the logs?
Your test will be off if you call the slow Date(), over and over again
in System.out.println (new Date ()); You should use the system
currenttimemillis.
Alos, you might want to use an ArrayList
But I have 8 line in log for each element read :
Maybe it's comming from here ? How can I disable the log ? Is it maybe
JBoss
who activate this ?
Oh my yes, 8 lines of output per element will slow things down plenty.
You need to turn the log4j log level for the jcs classes up to INFO or
WARN.
Running the same test as standalone in a main :
Avant le test
Tue Jan 20 18:47:30 EST 2004
Tue Jan 20 18:47:30 EST 2004
Tue Jan 20 18:47:30 EST 2004
Apres le test
:((( Now it's sure, it come from JBoss, but why and where ? :(
