This is continuation of previous post SSD Thrashing and RAMDrive, I have created a 512MB RamDrive and mapped it as R Drive. My Temp directories are located on RamDrive and so is the data directory for Chrome. With this arrangement and heavy use of chrome I could see some good benefits- due to holiday season I have spent a lot of time on my laptop (~8-10 hours or usage every day). And have a graph to show about the usage:
I installed Windows8.1 on 19 Dec, so starting with ~55 GB Host Writes and then followed by various updates and Visual Studio installation and internet browsing (youtube and pluralsight) till 22-Dec. On 23-Dec I installed RAMDrive but continued my trend of internet access and you can see the how the Host Writes dropped. Today (31-Dec) was 3 attempts at installing a big Windows update (~800 MB each time), thus the increase in Host Writes.
Anyway the point is: using RamDrive saves un-necessary SSD thrashing and you can feel browsers being very snappy (much snappier than what it was on SSD). For comparison here are the results for data transfer speed between HDD RAM (Laptop DDR3L and Desktop DDR3) and SSD.
Look at the difference for yourself. Also note 4K results are very important in real life- as OS/Browsers keep writing/reading small chunks of data consistently- here RAMDrive is almost order of magnitude faster.
This turned out pretty good so far on Windows. I had mixed results on OS X Yosemite. One of the bigger issues as it turned out is kext signing. Since OCZ ARC 100 is not supported/sold by Apple (or I did not paid Apple Tax for SSD), TRIM is disabled on Yosemite. These ArsTechnica articles have good information about why TRIM is so important. After spending quite some time investigating how to enable TRIM natively (and running for a week with disabling kext signing) I eventually decided to go back to my old Seagate Momentus XT HDD.