Hi, On Friday 01 May 2009 19:38:53 Atte André Jensen wrote: > Arnold Krille wrote: > > Both use threads to split their work, again there is no reason they have > > all their threads running on the same core. In fact one of the reasons to > > use threads is to make use of multiple cores within one app. > But doubling the load (for instance by adding more voices to ams) makes > *both* threads rise by (about) 100%. Wouldn't you expect for instance > gui threads to stay the same. I looked at your screenshot. As I am not familiar with your [ah]top, only with plain old top: 1) It reports different TIME+ values for the different threads. So they are basically not doing the same which is a good thing but maybe 2) your top has a problem with CPU% with multiple threads and reports the apps total for each thread... > Other cpu heavy processes seem to use only > one core, for instance building stuff from source. Also... Here building stuff from source uses 10 of 8 cores. "-j X" is your friend and rule of thumb says that X should be number_of_cores+1 to keep your room warm. Have fun, Arnold
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
