| |||||||||||||
The Tux3 filesystem returnsThe Tux3 filesystem returnsPosted Jan 2, 2013 8:43 UTC (Wed) by daniel (subscriber, #3181)In reply to: The Tux3 filesystem returns by keeperofdakeys Parent article: The Tux3 filesystem returns
Maybe that could be fixed by having a way to preload vast amounts of disk volume to cache. Anyway, I agree, spinning down is useful mainly for volumes that are either completely offline or have long periods of inactivity. Like three of the four disks in my workstation right now, which spend most of their time spun down courtesy of noflushd. BTW, the fourth disk will be changed out for a SSD pretty soon. Not doing so is just cruel and unusual self inflicted punishment.
(Log in to post comments)
The Tux3 filesystem returns Posted Jan 2, 2013 8:47 UTC (Wed) by keeperofdakeys (subscriber, #82635) [Link]
Unless 'cache' is an SSD (which is quite rare), you aren't going to be able to spin down a drive anyway (you also can't control the cache located in most harddrives, since it's for a different purpose). Personally I'm not a fan of this SSD cache phase, waste of an SSD when you could dedicate it to your root OS.
The Tux3 filesystem returns Posted Jan 2, 2013 21:40 UTC (Wed) by daniel (subscriber, #3181) [Link]
Note that I'm already getting very effective results out of spinning down my disks. I just take care which data I put on which disk. Spinning down the root volume effectively would be trickier, but doable.
By aggressive caching I meant preemptively reading big linear chunks of volume into host memory, a behaviour we plan to support after more pressing issues are under control. Spindown isn't our immediate priority by any means, but we can probably help make it practical in more situations.
|
|||||||||||||