Enjoy the power while it lasts, but do not build a critical workflow that depends on manually setting this value. Conclusion: The Golden Rule of browser.cache.memory.capacity After thousands of words of technical detail, the most important advice is simple:
Increase the capacity to store more assets in RAM, reducing reliance on the slower disk cache. Profile 2: The User on Constrained Hardware Scenario: You use an older laptop with only 2 GB of RAM. Firefox’s automatic mode attempts a 16 MB cache, but every tab you open pushes your system into swap memory (using the hard drive as fake RAM), causing the entire OS to freeze. Browser.cache.memory.capacity
This preference dictates exactly how much of your computer’s RAM (Random Access Memory) Firefox is allowed to use for storing web content temporarily. Unlike disk-based caches that save assets to your hard drive or SSD, the memory cache is the elite, lightning-fast tier of storage. When configured correctly, it can make page reloads feel instantaneous. When left at its default—or configured incorrectly—it can lead to sluggish performance, excessive memory usage, or wasted resources. Enjoy the power while it lasts, but do
The engineers at Mozilla have spent years tuning the automatic memory cache algorithm to balance speed, memory pressure, and disk usage. For the vast majority of users, the default setting provides 95% of the performance possible with zero risk. Firefox’s automatic mode attempts a 16 MB cache,
However, for the power user with 32 GB of RAM, setting this to 262144 (256 MB) can shave milliseconds off every tab switch. For the developer, setting it to 0 can be a lifesaving debugging tool.
