<html><body>Hmm. I was hoping for good news that things had changed for the better :( . I want these files to be on the disk so I don't lose data in the case of failure. A common solution here is to acidify the program, but that is not acceptable from a usability standpoint. I don't want to have the user mess around with swap files and the like. When something goes wrong, I want to seamlessly start up where we left off without the user even knowing that something out of the ordinary happened. A tmpfs will do nothing for this case :)<br><br>Timothy<br><p><br>---------- Původní zpráva ----------<br>Od: Brandon Allbery <allbery.b@gmail.com><br>Datum: 10. 11. 2012<br>Předmět: Re: [Haskell-cafe] Hard drive thrashing with modern controllers</p><blockquote><div><div>On Sat, Nov 10, 2012 at 2:49 PM, <span><<a href="mailto:timothyhobbs@seznam.cz">timothyhobbs@seznam.cz</a>></span> wrote:<br><div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>import Control.Monad<br>foo = do<br> forever $ writeFile
"filename.foo" "Hello world!"<br><br>will that destroy those sectors of my SSD
after the rated 3000 write cycles?<br></div></blockquote><div><br></div><div>Check your OS; while the firmware of modern SSD devices does much of the work of rotating blocks of Flash around to mitigate this, the OS can help by using a TRIM operation. <a href="http://en.wikipedia.org/wiki/TRIM">http://en.wikipedia.org/wiki/TRIM</a></div>
<div><br></div><div>I personally would consider that rapidly changing files should be kept somewhere else such as tmpfs with periodic snapshots to nonvolatile storage.</div></div><div><br></div>-- <br><div><div>
brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net">ballbery@sinenomine.net</a></div>
<div>unix/linux, openafs, kerberos, infrastructure <a href="http://sinenomine.net">http://sinenomine.net</a></div></div><br>
</div>
</div></blockquote></body></html>