History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CACHE-151
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Rajeev Chaudhary
Votes: 3
Watchers: 5
Operations

If you were logged in you would be able to see more operations.
OSCache

limiting Cache size on disk

Created: 15/Mar/05 04:18 AM   Updated: 21/Jan/07 01:55 PM
Component/s: Persistence
Affects Version/s: 2.1
Fix Version/s: 3.0

Environment:
 cache.capacity=100
 cache.unlimited.disk=false
 cache.persistence.overflow.only=true are the defined properties
Issue Links:
Duplicate
 
This issue is duplicated by:
CACHE-153 cache.capacity does not restrict disk... Major Closed

Flags: Important


 Description  « Hide
cache.capacity=100
cache.unlimited.disk=false
cache.persistence.overflow.only=false
It will create 100 object on the disk.When 101 object is
there it will delete one to object from the cached object
and there will be still 100 only on the disk. This is OK

cache.persistence.overflow.only=true
In this case, after 100 object are cached in memory. From 101 object onwards all will be persisted on the hard disk.The number of object saved on the disked are unlimited and there is no restriction on it.

There should be some limitation of object that are cached on the disk when
cache.persistence.overflow.only=true


 All   Comments   Change History      Sort Order:
Frank Nestel - [29/May/05 07:47 AM ]
It looks like we then need two capacity settings, one for capacity in memory one for capacity on disk (maybe both can take the general capacity as a default or so).

We have a cache scenario here, where we need to go to disk for capacity reasons, but we could imagine to have the "most popular" items in memory. To do this very well one would need to enricht the API for the caching strategies, so that the strategy could to decide what to keep on disk and what to keep in memory.

Andres March - [29/May/05 10:40 AM ]
dup of 151