Dirk Munk wrote on 14/02/2019 19:13:
Gabriel wrote:
Dirk Munk wrote on 14/02/2019 14:51:
Dirk Munk wrote:
I'm using the 64 bit builds of WG9s.
I'm very happy with them in general.
However, after installing a new version of 2.49.5 a short while ago, I
experienced some weird problems like keystrokes that became garbled, very
sluggish responses etc. A new upgrade to 2.53 didn't help, so I tried to
figure out what might be the cause.
Then I had a hunch, and I checked the config file for the browser cache
setting. It was just about 0.5 GB, and I'm sure it was much bigger.
I've now increased browser.cache.memory.capacity to 2 GB (2097152), and all
problems are gone.
After increasing browser.cache.memory.capacity to 4 GB (4194304), the browser
runs even more smoothly. Nice.
What's the difference with the "let SM manage the size of my cache" preference?
That is the disk cache, so files on disk, I'm talking about the memory cache, in
RAM.
Maybe that setting is Windows only, because on my Mac I see SM using a lot of
RAM between 3 and 5 GB (I have 24 GB) and it's not so fast anyway (it often
freezes), even if the value for "browser.cache.memory.capacity" is "200000".
Shouldn't be the OS to decide the amount of RAM?
Do you know what "browser.cache.memory.max_entry_size" is about?
Thank you.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
