Paul B. Gallagher wrote:
Lee wrote:

On 2/25/19, Paul B. Gallagher <[email protected]> wrote:

OK, so the workaround for the CPU cap is to use less CPU time?

I think the "CPU cap" you're seeing is a single logical CPU running
100% busy.  If your system has four logical CPUs and one of them is
100% busy that'd be 25% overall cpu utilization.  If you're on windows
10 you can check by

start / Windows System / Task Manager
click on the performance tab, then cpu
right click on the graph, change graph to, logical processors

The Task Manager is how I know how much CPU is being used, and even though I didn't say so explicitly, I thought I implied that was my theory too, that one CPU is maxed out. Looking at the performance tab on my system, it already shows four separate graphs, one for each processor. But they all seem to be busy at roughly equal levels, so perhaps something else is going on.

And the way to do that is to reduce disk caching (which I'm
probably not doing since I have 5-6 GB of RAM free) by increasing
memory cache?

I think the suggestion is to reduce cpu usage by keeping more stuff
in memory & not wasting cpu cycles by sending stuff off to the disk (either swap or cache) & then reading it back in.

I heard that, but I'm skeptical. I don't think my system is stalling due to paging or caching to disk, but today's test will show whether Dirk's right or wrong.

Another possible scenario (I thought we grew out of this decades ago) is that the program doesn't know how to use all the available RAM, or something is denying it access beyond its allocation.

That is exactly what is happening! Seamonkey would love to use more RAM by putting more data in the memory cache, but the setting of 200 MB makes that impossible. It is not allowed to use more RAM. If you would set the memory cache to 16 GB (in theory), you would most likely see that Seamonkey only takes a very small amount of the 16 GB, it doesn't need more. To make this very clear, that 16 GB is not allocated to Seamonkey, but Seamonkey is allowed to ask for up to 16 GB from Windows if it needs more RAM.

But that wouldn't explain why the hangs occur when CPU usage reaches 25% and not when RAM usage approaches 8 GB (which is when I'd expect disk thrashing to start).

Yes it does. Seamonkey is so busy with its own housekeeping, trying to move data in and out from the cache, that it hardly has any time left for processing the data.

If all the applications on your system need more than 8 GB in total, then Windows will start swapping. That does not happen. Your problem is that Seamonkey reaches the maximum RAM limit it is allowed to use, but that is the result of the setting in the configuration file.

In fact, in the four years I've had this system, I've never seen CPU usage over about 26-27% no matter how hard I pushed it.



_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to