jakarta-jcs-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Smuts <asm...@yahoo.com>
Subject Re: Time to draw data from the JCS
Date Tue, 25 Jan 2005 18:43:24 GMT
It depends on the configuration.  If your unit test
has the log level for JCS set to debug, then it will
be much much slower.  If your unit tests is configured
to use a disk cache and the production test is not,
then the times could be affected, but not by that
much. . . .  Under all conditions that I've seen,
except for some 1.3 vm's on linux, JCS should operate
at under or around 2 times the speed of a hashtable. 
The JCS unit tests enforce that JCS be under 2.5 times
a hashtable for sequential key puts.  On 1.4 vm's it
exceeds this requirement by far.

I suspect that it is logging that is making the
difference between your production and test times.  


> > I am using the JCS cache, and I have a question:
> > I have noticed that if I put a reasonable number
> of
> > items into the cache, say 1000, and I draw a
> single
> > item from the cache, then depending on the point
> > from where I initiate the draw, the draw takes a
> > different amount of time.
> > 
> > For example, I have a stateless session bean, that
> > gets to the cache through a cache framework that
> we
> > have built.  The time taken to draw the items is
> > always 0 milliseconds, or in other words, below
> the
> > clock's resolution.
> > However, I have a unit tester that is a simple
> java
> > class.  For the same draw from this java class,
> the
> > time taken varies from between 300 milliseconds to
> > 500 milliseconds.  
> > 
> > Do you have any idea why there is such a
> difference?
> >  Any help you could provide would be appreciated. 
> > Thanks in advance,

To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org

View raw message