<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: tmpfs vs. ext3 performance on large file sets</title>
	<atom:link href="http://slacy.com/blog/2008/08/tmpfs-vs-ext3-performance-on-large-file-sets/feed/" rel="self" type="application/rss+xml" />
	<link>http://slacy.com/blog/2008/08/tmpfs-vs-ext3-performance-on-large-file-sets/</link>
	<description>This site is solar powered!</description>
	<lastBuildDate>Fri, 12 Mar 2010 07:09:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: blinkoryoumissit</title>
		<link>http://slacy.com/blog/2008/08/tmpfs-vs-ext3-performance-on-large-file-sets/comment-page-1/#comment-18076</link>
		<dc:creator>blinkoryoumissit</dc:creator>
		<pubDate>Wed, 03 Mar 2010 22:26:08 +0000</pubDate>
		<guid isPermaLink="false">http://slacy.com/blog/?p=603#comment-18076</guid>
		<description>Yea ive done a lot more research on the issue, if you storing a varible directory size then its a bit difficult as in the system might start swapping, but if you caculate a forecasted tmpfs size allocation it should be alight, as in txt files but its possible to use symbolic links that could be an idea, i let you think on it.. peace out..</description>
		<content:encoded><![CDATA[<p>Yea ive done a lot more research on the issue, if you storing a varible directory size then its a bit difficult as in the system might start swapping, but if you caculate a forecasted tmpfs size allocation it should be alight, as in txt files but its possible to use symbolic links that could be an idea, i let you think on it.. peace out..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blinkorumissit</title>
		<link>http://slacy.com/blog/2008/08/tmpfs-vs-ext3-performance-on-large-file-sets/comment-page-1/#comment-17590</link>
		<dc:creator>blinkorumissit</dc:creator>
		<pubDate>Sun, 15 Feb 2009 16:19:46 +0000</pubDate>
		<guid isPermaLink="false">http://slacy.com/blog/?p=603#comment-17590</guid>
		<description>Yes do it but, it all depends on what your storing, if it is riskless data, as in &#039;one doesnt care whether it will be destoryed or not &#039; then go for it, another idea is to some how create a one read one write to the harddisk asin have file in and out put onto a queue then place a &quot;copy&quot; of the whole readable file in tmpfs so if in the event of  system crash, system faliure, it will be alright you just restore the stored copy, but then again, dont quote me word for word, that was an idea, their are other factors to consider, just email me!!!</description>
		<content:encoded><![CDATA[<p>Yes do it but, it all depends on what your storing, if it is riskless data, as in &#8216;one doesnt care whether it will be destoryed or not &#8216; then go for it, another idea is to some how create a one read one write to the harddisk asin have file in and out put onto a queue then place a &#8220;copy&#8221; of the whole readable file in tmpfs so if in the event of  system crash, system faliure, it will be alright you just restore the stored copy, but then again, dont quote me word for word, that was an idea, their are other factors to consider, just email me!!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
