From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 30712] New: Slow transitioning AMD ondemand CPU because of wrong sampling_rate
Date: Mon, 7 Mar 2011 21:54:03 GMT [thread overview]
Message-ID: <bug-30712-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=30712
Summary: Slow transitioning AMD ondemand CPU because of wrong
sampling_rate
Product: Power Management
Version: 2.5
Kernel Version: 2.6.37
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@vger.kernel.org
ReportedBy: justincase@yopmail.com
Regression: No
This bug has been previously reported on the Debian bugtracker, please have a
look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614256 as it contains
much more information.
Using the ondemand governor, the time taken for the CPU to rise to max
frequency is noticeable by the user and impact global performance. Setting
sampling_rate to sampling_rate_min makes the the CPU perform much faster
transitions.
On this processor :
AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
Down freq: 1000MHz / Up freq: 2200MHz
I have:
/sys/devices/system/cpu/cpufreq/ondemand/sampling_rate:109000
/sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_min:10900
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency:109000
This simple command solves the problem:
cat sampling_rate_min >| sampling_rate
So, I suppose the default values are not optimal. In contrast, I have an
Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz, and the three values mentioned
above are all equal to 10000 on this processor.
I did some dirty benchmarking using the following command:
dd if=/dev/zero of=/dev/null bs=300k count=1000
Here are my results in GB/s (several averages) for the AMD CPU:
--------------
performance :
7.61 / 7.61 / 7.61 / 7.56 / 7.37
ondemand (no-tweaking) :
4.83 / 4.68 / 4.73 / 5.14 / 5.51 / 5.37
ondemand (sampling_rate = rampling_rate_min, i.e. default/10) :
7.00 / 7.07 / 7.03 / 7.06 / 7.02 / 7.01 / 7.04
--------------
Please see the original Debian bug report for more information.
Thanks
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-03-07 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 21:54 bugzilla-daemon [this message]
2011-03-07 21:54 ` [Bug 30712] Slow transitioning AMD ondemand CPU because of wrong sampling_rate bugzilla-daemon
2011-03-08 9:17 ` bugzilla-daemon
2011-03-15 4:59 ` bugzilla-daemon
2011-03-24 17:30 ` bugzilla-daemon
2011-03-24 21:58 ` bugzilla-daemon
2011-03-28 1:47 ` bugzilla-daemon
2011-03-28 5:28 ` bugzilla-daemon
2011-03-29 15:29 ` bugzilla-daemon
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=bug-30712-12968@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.org \
/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