Browser.cache.memory.capacity: Difference between revisions
From MozillaZine Knowledge Base
Jump to navigationJump to search
Alice Wyman (talk | contribs) (→Recommended settings: clarified that new setting to be entered is in KB not MB... shouldn't the table to changed to reflect cache values in '''KB'''?) |
(recommended settings are for recommended settings only - not what the values mean. also, there's no evidence that having this at a high value would cause a memory leak) |
||
| Line 12: | Line 12: | ||
|- | |- | ||
| 32MB | | 32MB | ||
| | | 2,048KB | ||
|- | |- | ||
| 64MB | | 64MB | ||
| | | 4,096KB | ||
|- | |- | ||
| 128MB | | 128MB | ||
| | | 8,192KB | ||
|- | |- | ||
| 256MB | | 256MB | ||
| | | 14,336KB | ||
|- | |- | ||
| 512MB | | 512MB | ||
| | | 22,528KB | ||
|- | |- | ||
| 1GB | | 1GB | ||
| | | 32,768KB | ||
|- | |- | ||
| 2GB | | 2GB | ||
| | | 45,056KB | ||
|- | |- | ||
| 4GB | | 4GB | ||
| | | 59,392KB | ||
|} | |} | ||
===0=== | ===0=== | ||
Do not cache decoded images and chrome in memory. | Do not cache decoded images and chrome in memory. | ||
===Any positive integer=== | ===Any positive integer=== | ||
Maximum amount of memory in '''KB''' to use to cache decoded images and chrome. (Thunderbird default: 4096. Minimo default: 256) | Maximum amount of memory in '''KB''' to use to cache decoded images and chrome. 1MB = 1024KB. (Thunderbird default: 4096. Minimo default: 256) | ||
==Caveats== | ==Caveats== | ||
| Line 45: | Line 45: | ||
==Recommended settings== | ==Recommended settings== | ||
Users who are having problems with memory consumption can try setting the value to something lower than specified in the table above to lower memory consumption. | Users who are having problems with memory consumption can try setting the value to something lower than specified in the table above to lower memory consumption. Users who have no problems with memory should leave it at -1. | ||
Users who have no problems with memory should leave it at -1. | |||
==First checked in== | ==First checked in== | ||
Revision as of 15:26, 4 January 2006
Background
When a page is loaded, it can be cached so it doesn't need to be rerendered to be redisplayed. This preference controls the maximum amount of memory to use for caching decoded images and chrome (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)
| RAM | Cache |
|---|---|
| 32MB | 2,048KB |
| 64MB | 4,096KB |
| 128MB | 8,192KB |
| 256MB | 14,336KB |
| 512MB | 22,528KB |
| 1GB | 32,768KB |
| 2GB | 45,056KB |
| 4GB | 59,392KB |
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. 1MB = 1024KB. (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.
Recommended settings
Users who are having problems with memory consumption can try setting the value to something lower than specified in the table above to lower memory consumption. Users who have no problems with memory should leave it 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
