Lee wrote:
On 2/26/19, Paul B. Gallagher <[email protected]> wrote:
Yesterday, I wrote:
Pref set to 1048576. Let's see what happens.
OK, 24 hours of life with a larger memory cache have shown:
1) No dramatic improvement in overall performance;
2) A lack of hangs when SM reaches 25% CPU usage -- it hasn't reached
that level during the test period. Rather, it seems to peak at 15–18%.
So there may well be something to what Dirk Munk advised. I'll keep
running with this pref setting and watch for the hangs I used to get
regularly. When opportunities arise, I'll push it harder.
What does about:cache show for memory now?
I'm not seeing any hangs w/ seamonkey and still have the default
Maximum storage size: 200000 KiB
with
Storage in use: 29998 KiB
At the moment, I'm not pushing it, but here's what it shows:
memory
Number of entries: 1212
Maximum storage size: 1048576 KiB [that's my user-set limit]
Storage in use: 54939 KiB
And according to task manager, seamonkey is using 305MB of memory
According to Task Manager, SM is using 1,051,192 KB of memory. Under
peak load, I would expect that to double; I haven't yet seen it reach 3 GB.
I did have some trouble this afternoon as I was perusing Google News.
For some stories, I clicked "View full coverage" and each time I did, SM
hung. As before, CPU peaked at 26–27% and RAM usage was a little over 2
GB. After two or three minutes, the cursor returned to its usual arrow
shape and CPU usage fell to under 10%. But the next time I clicked "View
full coverage," it was like standing on the brakes again.
--
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
