public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jayson King <dev@jaysonking.com>
To: linux-kernel@vger.kernel.org
Cc: a.p.zijlstra@chello.nl, mingo@elte.hu
Subject: Re: problem with "sched: revert back to per-rq vruntime"?
Date: Tue, 30 Dec 2008 13:37:47 -0600	[thread overview]
Message-ID: <495A788B.3010001@jaysonking.com> (raw)
In-Reply-To: <495948E0.8040502@jaysonking.com>

Here's some times using bash, for example. Let me know if there are some 
other tests I can do.

It shows on vanilla 2.6.28, a huge increase in latency (about 37X to 
39X) starting bash -i when the CPU is loaded with 100% nice tasks, 
relative to idle CPU. But after reverting 
f9c0b0950d5fd8c8c5af39bc061f27ea8fddcac3 the latency increase is not as 
great (about 2X).

# running bash -i on vanilla 2.6.28,
# with idle CPU
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.020s
user    0m0.008s
sys     0m0.014s
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.020s
user    0m0.014s
sys     0m0.005s
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.020s
user    0m0.008s
sys     0m0.009s



# running bash -i on vanilla 2.6.28,
# with 100% nice CPU usage
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.753s
user    0m0.011s
sys     0m0.011s
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.752s
user    0m0.012s
sys     0m0.012s
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.786s
user    0m0.010s
sys     0m0.008s



# running 2.6.28 reverted f9c0b0950d5fd8c8c5af39bc061f27ea8fddcac3,
# with idle CPU
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.021s
user    0m0.012s
sys     0m0.007s
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.020s
user    0m0.012s
sys     0m0.011s
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.020s
user    0m0.011s
sys     0m0.012s



# running 2.6.28 reverted f9c0b0950d5fd8c8c5af39bc061f27ea8fddcac3,
# with 100% nice CPU usage
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.043s
user    0m0.010s
sys     0m0.009s
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.046s
user    0m0.011s
sys     0m0.007s
[jayson@atlas tmp]$ time bash -i -c 'exit'
exit

real    0m0.047s
user    0m0.011s
sys     0m0.006s




Jayson


  parent reply	other threads:[~2008-12-30 19:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 22:02 problem with "sched: revert back to per-rq vruntime"? Jayson King
2008-12-29 22:11 ` Jayson King
2008-12-30 19:37 ` Jayson King [this message]
2008-12-31 16:26   ` Mike Galbraith
2008-12-31 20:17     ` Jayson King
2009-01-01  7:46       ` [patch] " Mike Galbraith
2009-01-02  0:14         ` Jayson King
2009-01-02 11:16           ` Mike Galbraith
2009-01-02 20:38             ` Jayson King
2009-01-05  7:54             ` Peter Zijlstra
  -- strict thread matches above, loose matches on Subject: below --
2008-12-29  8:23 Jayson King

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=495A788B.3010001@jaysonking.com \
    --to=dev@jaysonking.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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