Google-chrome – Chrome writes too much to SSD

google-chromesession-restoressdsymbolic-linkusb

As the session recovery feature in Chrome and Firefox does a lot of disk writing which isn't good for an SSD, Firefox has a solution, but I'm not aware of one for Chrome. There are workarounds that involve using a USB/SD card/external hard drive for the Chrome profile folder. You could either use the "c:\Program Files (x86)\Google\Chrome\Application\chrome.exe"–user-data-dir=…" command to move the profile folder to the external drive, or create a symbolic link on the local appdata folder that points to a external drive folder. The result of this would be that on the one hand the actual installed program folder would be on the SSD itself so Chrome would presumably run on the SSD's resources, while on the other hand the profile/appdata folder and the cache would be on the external drive, so Chrome wouldn't be writing to the SSD.

Are there any disadvantages to these workarounds (i.e. putting the Chrome profile folder on an external drive)? Which would be the better one? And does anyone have a better workaround or solution to this?

Thank you very much.

Best Answer

I happen to have a lot of RAM available, so have configured /tmp as a RAM-disk, reducing some of the wear and tear on the SSD (it's also faster).

Extending this idea, I symlinked ~/.cache to /tmp/home/[userid]/.cache.

A large amount of Chrome data now ends up there:

$ du -s -m ~/.cache/*  |  sort -n  | tail -3
4   /home/ray/.cache/tracker
416 /home/ray/.cache/google-chrome
529 /home/ray/.cache/thumbnails

That's nearly a gigabyte, all from Chrome, all in fast access ROM.

Yes, when I reboot it will all get lost and Chrome will be a little slower for a while, but for me that might not happen for many months.

Related Question