From: Bill Davidsen <davidsen@tmr.com>
To: Matthew <jackdachef@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@chiara.csoma.elte.hu
Subject: Re: [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20
Date: Sun, 30 Sep 2007 19:54:42 -0400 [thread overview]
Message-ID: <47003742.5090604@tmr.com> (raw)
In-Reply-To: <e85b9d30709290411u4f48d716o3260bab7d71261ff@mail.gmail.com>
Matthew wrote:
> Hi Ingo & everbody on the list,
>
> first of all: many thanks for developing this great scheduler (also:
> kudos to Con Kolivas for having developed SD & CK-patchset)
>
> (this is my second mail to this list and I hope I'm doing everything right)
>
> I'm doing some backup during work right now: rsyncing my home
> partition (nearly 180 GB) to another harddrive locally &
> since I'm running compiz-fusion, openoffice and gnome, therefore am in
> some real "working environment" I thought:
> give Ingo's new scheduler a test-ride during heavy load ;)
>
> first some impressions:
> cpu load balancing looks great again (pretty symmetrical loading on
> both cores - it looks pretty similar to 19.1 if not better if I recall
> right),
> v20 wasn't that "good-looking" ;) (with gnome-system-monitor)
>
> both cpus have a continous load of ~ 70% right now so I'll be
> starting up 9 instances of glxgears, below are some output & details
> of my system
> (cpu frequency switching is disabled since it doesn't work right now
> with the current bios version)
>
> short summary: unfortunately after starting glxgears everything
> stuttered a lot, don't know if it's expactable during that heavy load
> - just wanted to let you know; after having closed each instance of
> glxgears, everything was fine again ...
>
> cat /proc/sched_debug
> Sched Debug Version: v0.05-v22, 2.6.23-rc8-cfs-v22 #1
> now at 3890590.670323 msecs
> .sysctl_sched_latency : 20.000000
> .sysctl_sched_nr_latency : 0.000020
> .sysctl_sched_wakeup_granularity : 2.000000
> .sysctl_sched_batch_wakeup_granularity : 25.000000
> .sysctl_sched_child_runs_first : 0.000001
> .sysctl_sched_features : 3
>
Try setting features to 14. That helps my similar issues.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-09-30 23:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 11:11 [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20 Matthew
2007-09-30 15:43 ` Ingo Molnar
[not found] ` <e85b9d30709300943rded9801xddc6ca0a4773ff53@mail.gmail.com>
2007-09-30 16:45 ` Fwd: " Matthew
2007-09-30 17:27 ` Ingo Molnar
2007-09-30 23:54 ` Bill Davidsen [this message]
2007-10-02 9:06 ` Matthew
-- strict thread matches above, loose matches on Subject: below --
2007-09-26 11:13 Ingo Molnar
2007-09-26 13:33 ` S.Çağlar Onur
2007-09-26 13:48 ` Ingo Molnar
2007-09-28 20:26 ` Alejandro Riveira Fernández
2007-09-29 2:20 ` Henrique de Moraes Holschuh
2007-09-29 16:51 ` Alejandro Riveira Fernández
2007-09-30 15:26 ` Ingo Molnar
2007-10-02 18:12 ` Alejandro Riveira Fernández
2007-10-26 18:56 ` [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8,v2.6.21.7, v2.6.20.20 Fortier,Vincent [Montreal]
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=47003742.5090604@tmr.com \
--to=davidsen@tmr.com \
--cc=jackdachef@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@chiara.csoma.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.