<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Latest posts for the topic "DSO and memory/persistent configuration."]]></title>
		<link>http://forums.terracotta.org/forums/posts/list/5.page</link>
		<description><![CDATA[Latest messages posted in the topic "DSO and memory/persistent configuration."]]></description>
		<generator>JForum - http://www.jforum.net</generator>
			<item>
				<title>DSO and memory/persistent configuration.</title>
				<description><![CDATA[  I know that if i have lets say a collection of objects in memory and clustered using DSO, if i run out of space in memory, it will write objects from heap to disk.     

I want to know if it is possible to set the configuration to allow no objects to be stored in memory and when objects are added to this "clustered" collection they are written to the disk on the node...

basically identical to OSCache implementation of caching , they have a setting where i can specify how many objects that will be stored in the in-memory cache, with excess spilling over to the disk.  you can set a setting to in-memory =0, so all objects cached will be writing to the file system.

thx.]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/114.page#412</guid>
				<link>http://forums.terracotta.org/forums/posts/list/114.page#412</link>
				<pubDate><![CDATA[Thu, 11 Jan 2007 03:57:01]]> GMT</pubDate>
				<author><![CDATA[ Pharaoh]]></author>
			</item>
			<item>
				<title>Re:DSO and memory/persistent configuration.</title>
				<description><![CDATA[ Yes, Terracotta's virtual memory implementation feature provides you some knobs to control how much of the clustered object graph resides on the L1 (application server) and how much resides on L2 (the Terracotta Server) and on disk attached to L2.

See the discussion at http://forums.terracotta.org/forums/posts/list/97.page

So in the use-case you describe, you'd set <b>l1.cachemanager.threshold</b> Java System property to something very low (default is 70, i.e. the evictor runs when heap utilization gets to 70%) to ensure that cache eviction runs frequently and the amount of application-server heap consumed by your cache is minimal. 

Hope that helps.
Cheers
]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/114.page#413</guid>
				<link>http://forums.terracotta.org/forums/posts/list/114.page#413</link>
				<pubDate><![CDATA[Thu, 11 Jan 2007 04:46:36]]> GMT</pubDate>
				<author><![CDATA[ zeeiyer]]></author>
			</item>
			<item>
				<title>Re:DSO and memory/persistent configuration.</title>
				<description><![CDATA[ I'm curious, how does Terracotta determine which parts of the graph to evict?  Does it use an LRU algorithm?]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/114.page#415</guid>
				<link>http://forums.terracotta.org/forums/posts/list/114.page#415</link>
				<pubDate><![CDATA[Thu, 11 Jan 2007 08:19:09]]> GMT</pubDate>
				<author><![CDATA[ anodos]]></author>
			</item>
			<item>
				<title>Re:DSO and memory/persistent configuration.</title>
				<description><![CDATA[ Not exactly. It's a combination of LFU and LRU in both the server cache and the client cache. Probably the best place to get a detailed description would be the tc-dev mailing list.

Cheers,
Steve]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/114.page#416</guid>
				<link>http://forums.terracotta.org/forums/posts/list/114.page#416</link>
				<pubDate><![CDATA[Thu, 11 Jan 2007 09:24:49]]> GMT</pubDate>
				<author><![CDATA[ steve]]></author>
			</item>
	</channel>
</rss>