All that talk about non-volatile ram, got me thinking about ramdisks again. I know friends of mine will groan if they read this. I was a big fan of ramdisks.
I can hear the whispers already (SSD’s dude!). I’ll let you guys do the benchmarking, but ramdisks are 10x faster.
Now that I had the ramdisk bug… again, I set out to look for one. There are some free ones, some paid. I wanted all the features possible so I ended up going with Radeon’s RAMdisk.
I set the windows temp variables to my R: drive. It’s set to save changes to it automatically in the background, and it loads on boot.
Almost the same as non-volatile ram.
The machine I’m typing this on as 32gb, so i put 10gb to the ram disk. a few things are running, Chrome, Blizzard client, Steam client, WordPress desktop, some background utils: Malwarebytes, Nvidia settings, Gaming mouse util. i have about 10gb free ram left.
I’ll test this baseline config and see where it goes. puttng ISO’s there temporarily sounds like a good use
I ended up putting the google chrome cache and code-cache into the ramdisk. Now that windows supports symlinks it was much easier to do.
Bottom line is it makes chrome lightning fast. and the ramdisk driver takes care of the issue of surviving a reboot.
I was happy enough with the results that I decided to do the same thing on the Linux side.
The process is Linux specific of course (create the ramdisk, add it to fstab, move the cache/code-cache/etc. to the ramdisk, create the symlinks, add a systemd service to call a bash file to do the save and restore on the ramdisk.
It’s even faster under Linux because that OS is just more efficient out of the box.
All this because I want to go on about the wonders of my current favourite coding environment.
Stay tuned. 🙂