yeah make a ram disk; it helps to save some writes/erases to your ssd (thus prolong the life of your ssd).
i use ram disk for work; i also put my cache, temporary files, or whatever that can be thrown away safely after shutdown in my ram disk. i use it for downloads too. normally i scan the ram disk after a day's work before i moved the files to my external drive; everything is super fast (except for the time to transfer those gigabytes of files from ram drive to spindle discs).
i use ram disk for work; i also put my cache, temporary files, or whatever that can be thrown away safely after shutdown in my ram disk. i use it for downloads too. normally i scan the ram disk after a day's work before i moved the files to my external drive; everything is super fast (except for the time to transfer those gigabytes of files from ram drive to spindle discs).
my current favorite: http://www.softperfect.com/products/ramdisk/
more can be found here: http://www.raymond.cc/blog/12-ram-disk-software-benchmarked-for-fastest-read-and-write-speed/
more can be found here: http://www.raymond.cc/blog/12-ram-disk-software-benchmarked-for-fastest-read-and-write-speed/
BNaughty wrote:
Could you be more specific with the size of your RAMDisk and what you have remapped Windows to store there? I haven't really explored the idea of using a RAMDisk because I have 2 SSD in RAID-0 and don't expect much performance increase... but I have began looking into it...
the idea is this:
1. ssd takes care of OS/app loading;
2. for data, we know ssd has a limited writes/erase cycles; to minimize writes/erases on ssd, a ram disk is a better alternative than a hdd; so you identify and remap a few directories that are used by the OS/apps to cater for high read/write operations.
what i need and do is very simple:
1. create a 16gb ramdisk and set up the ramdisk app;
2. map user temporary folder, cache folders of my firefox and chrome, and all browsers have their download folder pointed to ram disk.
a ram disk is still about 7 times faster than a raid0.
edit: note that i use the option that creates the ramdisk and directory structures on-the-fly; i do not create a ramdisk image that can be reused (i.e. preserve the state of ram disk contents and reloaded upon next boot).
