On 2/25/19, Paul B. Gallagher <[email protected]> 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.
I'd guess something else is going on. I just did a quick test of one program talking to another and got ~30% cpu busy overall - two processors were basically idle and the other two ~55% busy >>> 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. 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). 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. Open 4 dos command prompt windows & run this in each for /l %i in (1,1,1000000000) do @echo. > \nul I get 99% cpu busy :) Lee _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
