At my company, we are very interested in using an open source caching solution, but there is great concern that variances in the actual size of objects or data cached will result in unmanageable or unpredictable memory usage by a cache.
Proper tuning of a cache should in theory be the answer, but our cautious CTO is looking for extra protection. Most implementations seem to have caching expriy algorithms/policies based on max elements in the cache, but none I have seen allow a bounded memory constraint for a cache. I was wondering if anyone has implemented a custom policy that will evict from a cache based on its size in memory? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871942#3871942 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871942 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
