Browser.cache.memory.capacity: Difference between revisions
SteveChapel (talk | contribs) (→-1: put the most commonly used defaults first, as few users are still using Firefox 1.5) |
(→Background: mail & news use the cache as well) |
||
Line 2: | Line 2: | ||
==Background== | ==Background== | ||
When images are loaded, they can be cached so they don't need to be decoded or uncompressed to be redisplayed. This preference controls the maximum amount of memory to use for caching decoded images and chrome (application user interface elements). | When images are loaded, they can be cached so they don't need to be decoded or uncompressed to be redisplayed. For e-mail & newsgroups (i.e., Thunderbird and SeaMonkey), messages for IMAP accounts are cached as well in either disk or memory cache, unless synchronized locally already. This reduces the amount of network activity to reload previously viewed messages. This preference controls the maximum amount of memory to use for caching decoded images, messages, and chrome items (application user interface elements). | ||
==Possible values and their effects== | ==Possible values and their effects== |
Revision as of 01:53, 5 February 2011
Background
When images are loaded, they can be cached so they don't need to be decoded or uncompressed to be redisplayed. For e-mail & newsgroups (i.e., Thunderbird and SeaMonkey), messages for IMAP accounts are cached as well in either disk or memory cache, unless synchronized locally already. This reduces the amount of network activity to reload previously viewed messages. This preference controls the maximum amount of memory to use for caching decoded images, messages, and chrome items (application user interface elements).
Possible values and their effects
-1
Automatically decide the maximum memory to use to cache decoded images and chrome based on the total amount of RAM. (Default in all but Thunderbird and Minimo).
Physical RAM | Memory Cache (in KB) |
---|---|
32 MB | 2048 |
64 MB | 4096 |
128 MB | 6144 |
256 MB | 10240 |
512 MB | 14336 |
1 GB | 18432 |
2 GB | 24576 |
4 GB | 30720 |
8 GB and up | 32768 |
In Firefox 1.5 and SeaMonkey 1.0 and earlier versions, these defaults were the following:
Physical RAM | Memory Cache (in KB) |
---|---|
32 MB | 2048 |
64 MB | 4096 |
128 MB | 8192 |
256 MB | 14336 |
512 MB | 22528 |
1 GB | 32768 |
2 GB | 45056 |
4 GB | 59392 |
8 GB | 75776 |
See Bug 296538 for details.
0
Do not cache decoded images and chrome in memory.
Any positive integer
Maximum amount of memory in KB to use to cache decoded images and chrome (1 MB = 1024 KB). (Thunderbird default: 4096. Minimo default: 256.)
Caveats
- browser.cache.memory.enable must be true for this preference to take effect.
- Lowering this value causes less memory to be used but also increases the load time of previously visited pages and dialogs. Raising it has the opposite effect.
- To view current memory cache usage, put
about:cache?device=memory
in the Location Bar - This preference does not exist by default in applications other than Thunderbird.
Recommended settings
Users who are having problems and want to lower memory consumption can try setting the integer value to something lower than the memory cache setting given in the above table. 4096, which was the previous default value, is a good place to start because it will decrease memory usage for users with more than 64 MB RAM. Users who have no problems with memory should leave the setting at -1.
First checked in
Has an effect in
- Netscape (all versions since 6.1)
- Mozilla Suite (all versions since 0.9.1)
- Phoenix (all versions)
- Firebird (all versions)
- Firefox (all versions)
- Thunderbird (all versions)
- Minimo (all versions)
- SeaMonkey (all versions)
Related bugs
- Bug 85054 - Hard Drive grinds when disk cache set to zero.
- Bug 105344 - Memory cache pref should be a percentage of physical RAM
- Bug 204164 - Calculating memory cache as percentage of physical memory may not be such a good idea
- Bug 296538 - limit the memory cache to a reasonable value