Dirk Munk wrote:
Paul B. Gallagher wrote:
Dirk Munk wrote:
Also, keep in mind that the memory cache setting is a maximum value
that Seamonkey can use. At the moment I have the cache setting at 4
GB, but when I look at the task manager, the whole application uses
about 3.6 GB, That means Seamonkey is only using a fraction of that
allowed 4 GB.
I have 8 GB of RAM, but SM doesn't come anywhere near that. When I
have a lot going on, it seems to peak in the high one-gig or the low
two-gig range (maybe I'm not pushing it as hard as you do). At any
rate, that's not a limiting factor for me. (FWIW, I "let SeaMonkey
manage the size of my cache," but as noted upthread that's the disk
cache.)
But I have noticed that there does seem to be a cap on CPU usage. When
it gets to about 25%, SM slows to a crawl or even hangs (the cursor
turns to a spinning ring and the screen goes pale in Win7), and the
only solutions are either force-close it through Windows or wait three
to five minutes until it thinks things though. This even happens when
there are plenty of CPU cycles available. Other apps are unaffected,
so I just switch to another and do something useful while I'm waiting.
In that case try to change the memory cache by using about:config. Look
for the entry browser.cache.memory.capacity, it most likely shows
200000. Change it to 524288 (512 MB) or 1048576 (1 GB), and see what
happens. As you can see, I like to use values based on powers of 2.
Uh, what would that have to do with a CPU usage cap?
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
