Sully
April 15th, 2011, 10:27 AM
I recently came across documentation on how chrome is pretty disk I/O intensive, and read up on how it can 'possibly' effect the life of an SSD drive. I have never worried too much about that, but after reading how much chrome does, I got to thinking maybe I should cut out excessive I/O where I can.
Many of you might have seen that chrome offers no UI that can change the cache settings. There are some flags to do this though
--disk-cache-dir="path to cache directory" --disk-cache-size=size of cache in bytes
Anyway, after looking into this I found what some are doing is either redirecting the cache to a normal hdd or to a ram disk. Some are just setting the cache size to 1 which essentially creates a 1mb cache. You can also redirect the cache directory to '/dev/null' which then creates no cache that I can find. I have tried all 3 methods, but haven't decided yet which if any I will pursue beyond testing.
What are your thoughts?
Sul.
Many of you might have seen that chrome offers no UI that can change the cache settings. There are some flags to do this though
--disk-cache-dir="path to cache directory" --disk-cache-size=size of cache in bytes
Anyway, after looking into this I found what some are doing is either redirecting the cache to a normal hdd or to a ram disk. Some are just setting the cache size to 1 which essentially creates a 1mb cache. You can also redirect the cache directory to '/dev/null' which then creates no cache that I can find. I have tried all 3 methods, but haven't decided yet which if any I will pursue beyond testing.
What are your thoughts?
Sul.