[Haskell-cafe] Hard drive thrashing with modern controllers

[timothyhobbs at seznam.cz]

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 :)

Timothy


---------- Původní zpráva ----------
Od: Brandon Allbery <allbery.b at gmail.com>
Datum: 10. 11. 2012
Předmět: Re: [Haskell-cafe] Hard drive thrashing with modern controllers
"

On Sat, Nov 10, 2012 at 2:49 PM, <timothyhobbs at seznam.cz
(mailto:timothyhobbs at seznam.cz)> wrote:

" 
import Control.Monad
foo = do
 forever $ writeFile "filename.foo" "Hello world!"

will that destroy those sectors of my SSD after the rated 3000 write cycles?

"



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.  http://en.wikipedia.org/wiki/TRIM
(http://en.wikipedia.org/wiki/TRIM)
 



I personally would consider that rapidly changing files should be kept 
somewhere else such as tmpfs with periodic snapshots to nonvolatile storage.




-- 


brandon s allbery kf8nh                               sine nomine associates

allbery.b at gmail.com(mailto:allbery.b at gmail.com)                             
     ballbery at sinenomine.net(mailto:ballbery at sinenomine.net)
 
unix/linux, openafs, kerberos, infrastructure          http://sinenomine.net
(http://sinenomine.net)


 

"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/haskell-cafe/attachments/20121110/0ac235f8/attachment.htm>