On 2/25/19, Paul B. Gallagher <[email protected]> wrote: > Dirk Munk wrote: >> Paul B. Gallagher wrote: >>> 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? >> >> Caching to disk means reading and writing to disk, moving data around >> etc. That can be very CPU intensive, certainly when it's becoming very >> difficult to do so. > > 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 > 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. Lee _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
