From: Carl-Johan Kjellander <carl-johan@klarna.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Yong Zhang <yong.zhang0@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Sched_autogroup and niced processes
Date: Fri, 13 May 2011 15:36:28 +0200 [thread overview]
Message-ID: <BANLkTimvehoQkiiX5EuPB0ozVKoPk3tAbg@mail.gmail.com> (raw)
In-Reply-To: <1305292406.27263.20.camel@marge.simson.net>
On Fri, May 13, 2011 at 3:13 PM, Mike Galbraith <efault@gmx.de> wrote:
> On Fri, 2011-05-13 at 12:04 +0200, Ingo Molnar wrote:
>
>> Still, the other important problem is that we still seem to have a bug, even
>> with the cgroup set to low prio seti@home is sucking up CPU resources ...
>
> I don't see how. Other than the expected nice 19 overrun when nice 0
> group blocks, it works fine on my little Q6600 box.
Dunno if I've done it correct, but I've set 19 to the boinc manager
autogroup and some of
the seti@home clients, but the clients of course keep changing.
boinc 1172 0.1 0.0 81896 13408 ? SN May09 7:00
/usr/bin/boinc --check_all_logins --redirectio --dir /var/lib/boi
boinc 18983 82.6 0.3 98172 65224 ? RNl 08:10 364:28 \_
../../projects/setiathome.berkeley.edu/setiathome_enhanced
boinc 19162 83.0 0.4 98836 65948 ? RNl 08:16 360:32 \_
../../projects/setiathome.berkeley.edu/setiathome_enhanced
boinc 20295 84.6 0.3 98356 65468 ? RNl 08:57 332:42 \_
../../projects/setiathome.berkeley.edu/setiathome_enhanced
boinc 22980 82.5 0.3 97880 64992 ? RNl 09:32 295:55 \_
../../projects/setiathome.berkeley.edu/setiathome_enhanced
boinc 23760 81.6 0.3 98064 65168 ? RNl 09:59 270:25 \_
../../projects/setiathome.berkeley.edu/setiathome_enhanced
boinc 634 83.1 0.3 98224 65276 ? RNl 11:02 223:24 \_
../../projects/setiathome.berkeley.edu/setiathome_enhanced
boinc 31758 83.5 0.4 99116 65736 ? RNl 11:33 198:48 \_
../../projects/setiathome.berkeley.edu/setiathome_enhanced
boinc 5931 81.4 0.3 98456 65464 ? RNl 14:06 68:55 \_
../../projects/setiathome.berkeley.edu/setiathome_enhan
But when I build on Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz,
it's still a lot slower.
time make -j12
real 2m58.437s
user 10m58.010s
sys 1m45.610s
I can try the same thing at home on my Q6600 machine if I upgrade it,
cause of course the Core i7 doesn't actually have 8 cores, they are
just hyperthreaded. It might be a factor.
Or am doing something horribly wrong when I try to set the autogroup to 19?
/cjk
next prev parent reply other threads:[~2011-05-13 13:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 7:39 Carl-Johan Kjellander
2011-05-13 7:53 ` Yong Zhang
2011-05-13 8:05 ` Mike Galbraith
2011-05-13 8:22 ` Ingo Molnar
2011-05-13 8:41 ` Peter Zijlstra
2011-05-13 9:05 ` Ingo Molnar
2011-05-13 9:07 ` Peter Zijlstra
2011-05-13 9:14 ` Carl-Johan Kjellander
2011-05-13 9:29 ` Ingo Molnar
2011-05-13 9:46 ` Peter Zijlstra
2011-05-13 10:04 ` Ingo Molnar
2011-05-13 13:13 ` Mike Galbraith
2011-05-13 13:24 ` Peter Zijlstra
2011-05-13 13:36 ` Carl-Johan Kjellander [this message]
2011-05-13 14:06 ` Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTimvehoQkiiX5EuPB0ozVKoPk3tAbg@mail.gmail.com \
--to=carl-johan@klarna.com \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yong.zhang0@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®