carlbeech
May 27th, 2010, 08:50 PM
Ok,
I've had a look, but not spotted anything that seems related to this so here goes....
I'm running a laptop - and running 'powertop' I can see programs continually writing data to the disk, and stopping it being spun down, and therefore saving a lot of battery.
Does anyone know of a way to a) create a ramdisk, and b) to redirect arbitrary files to exist within the ramdisk, so that the continual updates take place there and allow the disk to spin down?
Ok - I can see the horror on faces already - these programs need to cache data etc - well a cache most of the time isn't really required long term - and if it came down to it, there'd be nothing wrong in copying the ramdisk value to the real disk say once every 10 minutes etc...
What does anyone think?
I know it should be really down to the developers of the code that's actually doing the writing e.g. kde / google chrome etc, however, I think the developers are mainly coding for the desktops where this isn't really a problem (or is it - after all, writing to a ramdisk would be faster wouldn't it... hmmm)
Comments / Solutions please!
Ta
Carl.
I've had a look, but not spotted anything that seems related to this so here goes....
I'm running a laptop - and running 'powertop' I can see programs continually writing data to the disk, and stopping it being spun down, and therefore saving a lot of battery.
Does anyone know of a way to a) create a ramdisk, and b) to redirect arbitrary files to exist within the ramdisk, so that the continual updates take place there and allow the disk to spin down?
Ok - I can see the horror on faces already - these programs need to cache data etc - well a cache most of the time isn't really required long term - and if it came down to it, there'd be nothing wrong in copying the ramdisk value to the real disk say once every 10 minutes etc...
What does anyone think?
I know it should be really down to the developers of the code that's actually doing the writing e.g. kde / google chrome etc, however, I think the developers are mainly coding for the desktops where this isn't really a problem (or is it - after all, writing to a ramdisk would be faster wouldn't it... hmmm)
Comments / Solutions please!
Ta
Carl.