Moving the /appdata and /roaming for firefox and chrome

[EarlZ]

I've been using an SSD for about 2.5 months and I've noticed a significant increase in writes from both firefox and chrome, I used to have a 2-3Gb/day max write now its going between 10-20Gb and its mostly from chrome and firefox, Im using SSD ready to monitor the writes on my SSD and it points that mozilla and google folders under /appdata are doing 90% of the writes as well as the mozilla folder under /roaming

I have a mechanical harddrive connected as well and would it be possible to move the said folders to that drive ?

 

[GeneO]

It is probably the caches that are doing the writing. You can redirect the caches to another disk. In Firefox you can change the location of the cache through the about:config configuration editor (type about:config in the url bar. The entry you want to change is browser.cache.disk.parent_directory.

For chrome, it is a command line option --disk-cache-dir





How To Change Google Chrome’s Cache Location And Size

Firefox cache location | InfoHole

 

[logicearth]

You do not need to minimize writes to your SSD drive. According to users here who run with SSDs and have done test thought the years and determined that writing to an SSD is not such a major issue.

See: http://www.sevenforums.com/general-discussion/202084-superfetch-ssd.html

 

[EarlZ]

It is probably the caches that are doing the writing. You can redirect the caches to another disk. In Firefox you can change the location of the cache through the about:config configuration editor (type about:config in the url bar. The entry you want to change is browser.cache.disk.parent_directory.

For chrome, it is a command line option --disk-cache-dir





How To Change Google Chrome’s Cache Location And Size

Firefox cache location | InfoHole

I'll give it a try.

You do not need to minimize writes to your SSD drive. According to users here who run with SSDs and have done test thought the years and determined that writing to an SSD is not such a major issue.

See: http://www.sevenforums.com/general-discussion/202084-superfetch-ssd.html

For the older generation 10,000 write cycles are pretty high compared to the 3,000 writes the new ones have but then again, Im sure I wont be keeping this drive for more than 3years anyway, just wanted to be sure that when I sell this off its not that worn out.

 

[GeneO]

It is probably the caches that are doing the writing. You can redirect the caches to another disk. In Firefox you can change the location of the cache through the about:config configuration editor (type about:config in the url bar. The entry you want to change is browser.cache.disk.parent_directory.

For chrome, it is a command line option --disk-cache-dir





How To Change Google Chrome’s Cache Location And Size

Firefox cache location | InfoHole

I'll give it a try.

You do not need to minimize writes to your SSD drive. According to users here who run with SSDs and have done test thought the years and determined that writing to an SSD is not such a major issue.

See: http://www.sevenforums.com/general-discussion/202084-superfetch-ssd.html

For the older generation 10,000 write cycles are pretty high compared to the 3,000 writes the new ones have but then again, Im sure I wont be keeping this drive for more than 3years anyway, just wanted to be sure that when I sell this off its not that worn out.

I have a 128GB drive that has 3000 erase cycles per cell. I have my browser caches, my Photoshop caches and scratch space and everything else on it. I have had it for a year and have reinstalled the OS on it and secure erased it quite few times. It still has 13 power-on years of life remaining before I hit that 3000 erase cycles at the rate I am going.

The wear leveling algorithms are really good now. Of course a 64 GB won't last that long and a 256 GB will last even longer.

 

[EarlZ]

Im using a Corsair ForceGT 240Gb if it matters, 2 months 7 days and 12hours of power time 932Gb of written data.

I got the Firefox cache move to work but not google chrome.

I have it setup to E:\Cache\FireFox