[haiku-development] Re: Reproducing system pauses.

  • From: Bruno Albuquerque <bga@xxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 29 Jul 2009 09:43:12 -0300

Fredrik Holmqvist wrote:
Just reusing this thread as I mistakenly erased the commit email where
Axel mentions the UI freezes were fixed.

Seems fixed here, at least I can't notice i while building
BezillaBrowser. I have 6GB mem (3,3GB in Haiku) and the cache seems to
only go up to about 400MB. Used mem is well below 200MB.

I did more testing and I also do not get the freezes anymore when compiling Haiku inside itself or doing an svn up on its tree. In fact, MP3s do not skip anymore under those conditions too so, in this respect the fix really improved things.

That said, I still get a UI freeze in ActivityMonitor at the exact point where my memory is all used up or right after it. Only now the freeze is only in ActivityMonitor. The rest of the system is ok unless I do something that tries to do IO at this point, like opening the Deskbar menu). This does immediatelly freezes the app in question. All frozen apps get back to life at the exactly same point that ActivityMonitor does.

A sidenote: I noticed while building and using ActivityMonitor. It
seems that the two cpu-graphs most of the time is the inverse of each
other (tested with -j2 and -j8) which may either be poor buildscripts
for Mozilla, or hinting at something else.
Bruno, you havn't noticed anything peculiar on your multicore machine,
like one with high cpu and three low?
It's probably nothing, but just thought I'd check.

What I noticed is that our scheduler tends to underutilize the CPUs. In Linux If i do jam -j4, almost all the time the 4 cores are pegged to 100% usage. In Haiku the cores oscillate a lot from 0 to 100% usage (even with -j8, that still happens).It could just be that we are waiting a lot more in IO in Haiku than in Linux tough.

-Bruno

Other related posts: