<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: JMX use cases</title>
	<atom:link href="http://blog.frankel.ch/jmx-use-cases/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.frankel.ch/jmx-use-cases</link>
	<description>Nicolas Fränkel blog</description>
	<lastBuildDate>Sun, 05 Feb 2012 22:28:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Stacey</title>
		<link>http://blog.frankel.ch/jmx-use-cases/comment-page-1#comment-1000</link>
		<dc:creator>Stacey</dc:creator>
		<pubDate>Sun, 27 Mar 2011 09:30:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankel.ch/?p=161#comment-1000</guid>
		<description>Hi Nicolas,
You make a good point regarding the separation of the cache instances in advance when dealing with Ehcache, and that flushing the cache is a good, quick solution if you haven’t done so. 
As someone who has worked with Ehcaches, I’ve also had to deal a lot with data eviction (meaning, the cache was down, got a miss on get, and now needs to retrieve data from the DB storage, but it’s full so it evicts some existing data). I just read a survey, according to which Ehcaches tend to be relatively small (usually 1-6 GB) compared to other data sets (1-20 GB), so this might be related to more frequent data eviction in second-level caches. The post discusses other Ehcache logging use cases (citing a survey on this issue by Teracotta Server): http://www.evidentsoftware.com/ehcache-logging-applicability-in-your-organization/. You might find it interesting.
Stacey</description>
		<content:encoded><![CDATA[<p>Hi Nicolas,<br />
You make a good point regarding the separation of the cache instances in advance when dealing with Ehcache, and that flushing the cache is a good, quick solution if you haven’t done so.<br />
As someone who has worked with Ehcaches, I’ve also had to deal a lot with data eviction (meaning, the cache was down, got a miss on get, and now needs to retrieve data from the DB storage, but it’s full so it evicts some existing data). I just read a survey, according to which Ehcaches tend to be relatively small (usually 1-6 GB) compared to other data sets (1-20 GB), so this might be related to more frequent data eviction in second-level caches. The post discusses other Ehcache logging use cases (citing a survey on this issue by Teracotta Server): <a href="http://www.evidentsoftware.com/ehcache-logging-applicability-in-your-organization/" rel="nofollow">http://www.evidentsoftware.com/ehcache-logging-applicability-in-your-organization/</a>. You might find it interesting.<br />
Stacey</p>
]]></content:encoded>
	</item>
</channel>
</rss>

