cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 19672] New: ondemand is slow
Date: Sun, 3 Oct 2010 21:08:43 GMT	[thread overview]
Message-ID: <bug-19672-12968@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=19672

           Summary: ondemand is slow
           Product: Power Management
           Version: 2.5
    Kernel Version: 2.6.35
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@vger.kernel.org
        ReportedBy: danielhollocher@gmail.com
        Regression: No


I find ondemand is allot slower than conservative for cpu bound tasks.  My
understanding is that performance wise, ondemand should be on par or slightly
faster than conservative.

My chip is an intel core 2 duo, I think 4300.  I am using 2.6.35 from Ubuntu.

On the kraken benchmark, ondemand completes in   34216.6ms +/- 2.3%   where as
conservative completes in   25699.3ms +/- 5.6%


Again, it is my understanding that ondemand should not have this much of a
slowdown.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-10-03 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03 21:08 bugzilla-daemon [this message]
2011-01-24 13:01 ` [Bug 19672] ondemand is slow bugzilla-daemon
2011-01-24 13:01 ` 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-19672-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