I've been thinking about what the best way in the terracotta world is
to deal with cache eviction.
If someone is building an app on top of terracotta and needs eviction
one might start with an LRUMap.
In a distributed world this has the problem of lock contention and
even has limits in the single vm
case depending on how time critical your cache is.
I naturally started investigating Clock caches (nice treatment over
in the derby world)
http://wiki.apache.org/db-derby/DerbyLruCacheManager
But in a distributed world this doesn't really completely solve the
problem either. It would be expensive
to replicate the changes to the items in the cache to all nodes and
the clock cache doesn't seem great
for a virtual heap because it seems it would fault in the world.
Seems like a user needs a partition-able concurrent cache eviction
policy. Has anyone done work in this area?
Cheers,
Steve
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
