Firefox might be killing your SSD, fix it with one simple step

Firefox might be killing your SSD, fix it with one simple step
Modern web browsers offer amazing functionality, speed, and performance. One of the best features without question is the session recovery. This allows us to continue where we left of as if we never closed the browser, even in case of computer crashing. There is a definite drawback though.

Serve the Home's Sergei Bobik has noticed that especially Firefox likes to write excessive amounts of data on your drive in case recovery is needed. It can potentially amount to tens of gigabytes a day.



Also it not only eats your storage but slowly kills your SSD, if that is what you use. SSD's only allow certain amount of writes before they expire. Thus, having programs constantly writing on them is not good for their lifespan.

This seems to happen with Firefox even though it is not used. Bobik noticed that within 45 minutes of having Firefox open it had written over gigabyte of data to an SSD. At this pace tens of gigabytes per day can be accumulated. In his recent calculations the same problem seems to be in Chrome as well and it could backup restoration data more than 24 GB/day.

There's an easy fix to improve your SDD's lifespan and reduce storage used by Firefox. You can change the frequency of the data writeup, by default it is done every 15 seconds. Switch the browser.sessionstore.interval parameter by typing about:config in your Firefox address bar. Notice that the time is in milliseconds (15 000 = 15 seconds, 300 000 = 5 minutes).

Written by: Matti Vähäkainu @ 28 Sep 2016 15:12
Tags
Firefox SSD Chrome
Advertisement - News comments available below the ad
  • 6 comments
  • Rezer

    I set it for 5 mins O_O

    28.9.2016 17:49 #1

  • matthuisman

    how about stopping it from crashing in the first place :)

    28.9.2016 23:49 #2

  • hearme0

    Yet the article doesn't include any means to limit this in Chrome.

    Sad!

    Private browse 100% of the time is what people SHOULD be doing.

    My Chrome is set to Incognito at all times.

    29.9.2016 12:28 #3

  • Bozobub

    That won't do a thing about this issue.

    29.9.2016 15:14 #4

  • hearme0

    Originally posted by Bozobub: That won't do a thing about this issue. Indeed you're right.....not sure what I was thinking but clearly i WASN'T!

    But I just changed it to 99999999 (or whatever the max number of 9's it'll take.)

    We'll see how that goes.

    Good article AD!!!


    But.......private browsing is highly recommended! ALWAYS! :)

    30.9.2016 00:45 #5

  • Bozobub

    Be aware, however, that setting too large an interval pretty much negates any meaningful chance of session recovery after a crash.

    30.9.2016 11:21 #6

© 2020 AfterDawn Oy

Hosted by
Powered by UpCloud