Re: Memory cache was reset after upgrade

[JAS]

Dirk Munk wrote:

JAS wrote:

Frank-Rainer Grahl wrote:

Why don't you just use "Let SeaMonkey manage the size of my cache" in
Advanced->Cache?

FRG


I am using Seamonkey 2.48 on Windows 7 wit 8gb memory and my browser
freezes all the time, I have
disk-cache set to "let Seamonkey set"
and in about:config I have the following:

browser.cache.memory.max_entry_size;5120

browser.cache.memory.enable;true
What should the settings be?

Thanks,
JAS


Frank-Rainer wrote the default setting is 20, so about 200MB. You
are running with 5MB, no wonder it's freezing.
I was running with 500MB, and that didn't work for me. I had big
problems, not just freezing. So now I'm running with 4GB (and lots of
open Tabs!!).

I have reset to 20 and we we see if it helps.
Thanks
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Dirk Munk]

JAS wrote:

Frank-Rainer Grahl wrote:

Why don't you just use "Let SeaMonkey manage the size of my cache" in
Advanced->Cache?

FRG

I am using Seamonkey 2.48 on Windows 7 wit 8gb memory and my browser 
freezes all the time, I have

disk-cache set to "let Seamonkey set"
and in about:config I have the following:

browser.cache.memory.max_entry_size;5120

browser.cache.memory.enable;true
What should the settings be?

Thanks,
JAS


Frank-Rainer wrote the default setting is 20, so about 200MB. You 
are running with 5MB, no wonder it's freezing.
I was running with 500MB, and that didn't work for me. I had big 
problems, not just freezing. So now I'm running with 4GB (and lots of 
open Tabs!!).

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[JAS]

Frank-Rainer Grahl wrote:

Why don't you just use "Let SeaMonkey manage the size of my cache" in
Advanced->Cache?

FRG

I am using Seamonkey 2.48 on Windows 7 wit 8gb memory and my browser 
freezes all the time, I have

disk-cache set to "let Seamonkey set"
and in about:config I have the following:

browser.cache.memory.max_entry_size;5120

browser.cache.memory.enable;true
What should the settings be?

Thanks,
JAS
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Dirk Munk]

Frank-Rainer Grahl wrote:
Default for browser.cache.memory.capacity seems to be 20. Never 
hand any problems here in countless installations. Is your disk 
slooo or an AV interfering?


FRG


No, but I always have many, many tabs open, and disk cache can not 
replace memory cache. Furthermore, when I have plenty of memory, why 
force Seamonkey to use the disk cache if I can give it plenty of memory?


Decades ago when I started in the IT, I already learned that giving 
applications plenty of memory really helps to speed up things. I once 
replaced a computer system (not x86) by another one that was basically 
the same. Just slightly faster CPUs and more memory. I set everything up 
to do as much as possible in memory, and the thing went 11 times faster 
than it predecessor.





Dirk Munk wrote:

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.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Dirk Munk]

Frank-Rainer Grahl wrote:
Why don't you just use "Let SeaMonkey manage the size of my cache" in 
Advanced->Cache?


FRG


As far as I'm aware, that's only for the disk cache.




Dirk Munk wrote:

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.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Frank-Rainer Grahl]

Default for browser.cache.memory.capacity seems to be 20. Never hand any 
problems here in countless installations. Is your disk slooo or an AV 
interfering?


FRG

Dirk Munk wrote:

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.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Frank-Rainer Grahl]

Why don't you just use "Let SeaMonkey manage the size of my cache" in 
Advanced->Cache?


FRG


Dirk Munk wrote:

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.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Dirk Munk]

Gabriel wrote:

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 "20".


That is the reason Seamonkey is freezing. Change the value to 2097152 (2 
GB), and see what happens. Seamonkey will only use as much as it needs.



Shouldn't be the OS to decide the amount of RAM?


No, every professional operating system has ways to limit the memory use 
(and other resources) of an application or a user. Suppose you change 
the memory cache to 10GB, then Seamonkey will request memory when it 
needs it, until that 10GB is consumed. It will then have to swap to disk.




Do you know what "browser.cache.memory.max_entry_size" is about?


If I interpret this correctly, it is the maximum size of an element on a 
web page. Each web page has elements like photographs etc. that are 
cached, but if such an element is bigger then this max_entry_size it 
will not be cached.




Thank you.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Gabriel]

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 "20".

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
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Dirk Munk]

Ray_Net wrote:

Dirk Munk wrote on 14-02-19 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.


I see in Preferences ONLY disk-cache-length ... Cannot see an option 
for memory-cache-length.

I see in about:config
browser.cache.memory.capacity with 200 000
I think that this is the same length than the disk cache.


Yes, you have to change the value with about:config.

The value of the disk cache and the memory cache do not have to be the same.

My notebook has 32GB, and I use the browser a lot. So why limit the 
memory cache to a low value?


Perhaps it should be an option in the Preferences window.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Dirk Munk]

David E. Ross wrote:

On 2/14/2019 3:22 AM, 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.


What is the name of the config file?


Type about:config where you normally type the URL of a web site.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Ray_Net]

Dirk Munk wrote on 14-02-19 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.


I see in Preferences ONLY disk-cache-length ... Cannot see an option for 
memory-cache-length.

I see in about:config
browser.cache.memory.capacity with 200 000
I think that this is the same length than the disk cache.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[David E. Ross]

On 2/14/2019 3:22 AM, 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.
> 

What is the name of the config file?

-- 
David E. Ross

Trump again proves he is a major source of fake news.  He wants
to cut off disaster funds to repair the damage caused by the
Woolsey Fire in southern California because he claims the state
fails to manage its forests properly.  The Woolsey Fire was NOT
a forest fire.  Starting in an industrial tract, it did not burn
through any forests.

See .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Dirk Munk]

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.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Gabriel]

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?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Memory cache was reset after upgrade

[Dirk Munk]

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.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey