Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Switched browser cache from disk (SSD) to RAM, about:cache still displaying in disk too

  • 3 replies
  • 1 has this problem
  • 1941 views
  • Paskiausią atsakymą parašė Harest

more options

Hi,

Talking briefly about the size of games nowadays and SSD, i checked some stuff and saw Firefox writing 4.5 Mo/s (= MB/s). I wanted to see what that was, and saw it's mainly firefox cache. From there i searched and found a few sites suggesting and showing the settings to change to switch from disk cache to RAM cache. I did so since i've enough free RAM from a little while now. Changed settings (in about:config):

  • browser.cache.disk.enable from true to false
  • browser.cache.disk_cache_ssl from true to false

browser.cache.memory.enable was already on true and browser.cache.memory.capacity on -1 (not sure it's the best setting, only displaying 32768 KiB in about:cache... Any insight appreciated).

The concern: Cf. title, about:cache is still displaying the cache is also on disk, while i don't see writings being done related to the cache on the SSD. Is it just a display error in this configuration, or is there something else? If it's an error, i guess i should report it if it's not already done on the appropriate platform after.

Also, i hope the 4.5 Mo/s was just a peak, because if it's constantly like that if you've Twitch opened for instance, that's a major issue. On a SSD like the Samsung 850 EVO 250GB with its small TBW of 75, that's slightly less than 193 full days.

Hi, Talking briefly about the size of games nowadays and SSD, i checked some stuff and saw Firefox writing 4.5 Mo/s (= MB/s). I wanted to see what that was, and saw it's mainly firefox cache. From there i searched and found a few sites suggesting and showing the settings to change to switch from disk cache to RAM cache. I did so since i've enough free RAM from a little while now. Changed settings (in '''about:config'''): * '''browser.cache.disk.enable''' from '''true''' to '''false''' * '''browser.cache.disk_cache_ssl''' from '''true''' to '''false''' '''browser.cache.memory.enable''' was already on '''true''' and '''browser.cache.memory.capacity''' on '''-1''' (not sure it's the best setting, only displaying 32768 KiB in about:cache... Any insight appreciated). The concern: Cf. title, about:cache is still displaying the cache is also on disk, while i don't see writings being done related to the cache on the SSD. Is it just a display error in this configuration, or is there something else? If it's an error, i guess i should report it if it's not already done on the appropriate platform after. ''Also, i hope the 4.5 Mo/s was just a peak, because if it's constantly like that if you've Twitch opened for instance, that's a major issue. On a SSD like the Samsung 850 EVO 250GB with its small TBW of 75, that's slightly less than 193 full days.''
Pridėtos ekrano nuotraukos

Modified by Harest

Chosen solution

Well, in case anyone wonders, it has been reported 7 years ago apparently, i should have searched over there before.

The answer as to why it's like that is because internally "disk cache" includes by default "memory cache". The result is a slightly irrelevant about:cache page.

I'll close the thread then as the only answer that can be given from there is the minor issue being handled.

Skaityti atsakymą kartu su kontekstu 👍 0

All Replies (3)

more options

Didn't you notice that there is no location mentioned for the disk cache just as for the other two caches ?

  • Storage disk location: none, only stored in memory
more options

@Cor-el: I did notice, but the data is still wrong so i'm wondering why.

more options

Chosen Solution

Well, in case anyone wonders, it has been reported 7 years ago apparently, i should have searched over there before.

The answer as to why it's like that is because internally "disk cache" includes by default "memory cache". The result is a slightly irrelevant about:cache page.

I'll close the thread then as the only answer that can be given from there is the minor issue being handled.

Modified by Harest