How to Cut Firefox’s SSD Write Volume by Adjusting Session Store Interval
Firefox can write 10‑30 GB of data to an SSD each day due to its default session‑store settings, but a simple change to the browser.sessionstore.interval parameter can dramatically reduce this wear, extending SSD lifespan.
According to external reports, Firefox may write a large amount of data to solid‑state drives (SSD), sometimes exceeding the manufacturer’s recommended daily write limits. ServeTheHome’s technical expert explained that, depending on the number of open tabs and windows, a default Firefox configuration can cause daily SSD writes of 10 to 30 GB. The main culprits are the recovery.js file, which stores thread information for crash recovery, and the cookie.* files that hold per‑site cookie data.
As users browse the web, Firefox periodically updates these files, generating continuous write operations. ServeTheHome’s Sergei Bobik noted that adjusting a single Firefox setting can limit the write activity of recovery.js.
Step‑by‑Step Fix
Enter about:config in the address bar and press Enter.
Search for the entry browser.sessionstore.interval and double‑click it to edit.
The default value for browser.sessionstore.interval is 15000 ms (15 seconds). To reduce write frequency, you can increase it to 300000 ms (5 minutes) or 1800000 ms (30 minutes).
Firefox is not the only browser with this issue; Google Chrome has been reported to write about 1 GB per hour, totaling roughly 24 GB per day.
Bobik warned SSD users that the nominal daily write endurance of many SSDs is around 20 GB, and browsers like Firefox (or Chrome) can consume more than half of that amount.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
ITPUB
Official ITPUB account sharing technical insights, community news, and exciting events.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
