[prev in list] [next in list] [prev in thread] [next in thread] 

List:       turbine-jcs-user
Subject:    RE: Re[2]: how JCS manages RAM? (object's size)
From:       Aaron Smuts <aasmuts () wisc ! edu>
Date:       2003-05-13 12:36:00
[Download RAW message or body]

http://jakarta.apache.org/turbine/jcs/IndexedDiskAuxCache.html

> -----Original Message-----
> From: Richard Lamuette [mailto:turbine.lammeland@laposte.net]
> Sent: Tuesday, May 13, 2003 3:58 AM
> To: Turbine JCS Users List; Aia?ae Aeaca?aa
> Subject: RE: Re[2]: how JCS manages RAM? (object's size)
> 
> use the aux disk cache
> 
> -----Message d'origine-----
> De : Andrei Glazachev [mailto:atl747@mail.ru]
> Envoye : mardi 13 mai 2003 10:33
> A : Turbine JCS Users List
> Objet : Re[2]: how JCS manages RAM? (object's size)
> 
> 
> Hello Richard,
> 
> Ok, but if I use jcs.region.testCache1.cacheattributes.MaxObjects=10
> and I put 5 objects which reserve 128 Mb of 128Mb All RAM.
> Can I put 6th object to cache?
> Is there any check for it?
> 
> RL> The MaxObjects is only used.
> 
> RL> -----Message d'origine-----
> RL> De : Андрей Глазачев [mailto:atl747@mail.ru]
> RL> Envoye : mardi 13 mai 2003 07:32
> RL> A : turbine-jcs-user@jakarta.apache.org
> RL> Objet : how JCS manages RAM? (object's size)
> 
> 
> RL> Good day All.
> 
> RL> When I put object to cache, JCS uses object's size to determine
cache
> RL> overflow?
> RL> Or JCS uses only parameter
> RL> "jcs.region.testCache1.cacheattributes.MaxObjects"?
> 
> --
> Andrei Glazachev mailto:atl747@mail.ru
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
turbine-jcs-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-jcs-user-help@jakarta.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
turbine-jcs-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-jcs-user-help@jakarta.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]