All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 54761] New: Variable cpu frequency causes to loose performance
Date: Mon,  4 Mar 2013 14:01:36 +0000 (UTC)	[thread overview]
Message-ID: <bug-54761-12968@https.bugzilla.kernel.org/> (raw)

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

           Summary: Variable cpu frequency causes to loose performance
           Product: Power Management
           Version: 2.5
    Kernel Version: Ubuntu 3.8.0-9.18-generic 3.8.1
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@vger.kernel.org
        ReportedBy: sworddragon2@aol.com
        Regression: No


Created an attachment (id=94381)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=94381)
Example application

In my sytsme is an AMD Phenom II X6 1045T with 6 cores and a scaling frequency
of "2700000 2000000 1400000 800000". I have noticed if a process is using ~the
half of cpu time of a core I'm getting heavy performance impacts if I'm using
the ondemand governor. Switching to the performance governor solves this
problem.

I have written a testcase in C which demonstrates this problem (compiled with
"gcc -o governor governor.c -lpthread"). The application creates 20 threads
(change NUM_THREADS in the code if needed) - every of them uses only a little
of cpu time. All threads will be executed on the same core. Here are the
differences between both governors:


ondemand:
The frequency of the related core goes up to 1400 MHz and the used cpu time of
this core is ~50%. The application needs ~7.17 seconds to be finished.

performance:
The frequency of the related core is constantly 2700 MHz and the used cpu time
of this core is ~25%. The application needs ~5.99 seconds to be finished.


The difference between the used cpu time is logical since the frequency is as
double so high. But both runs are far away from a 100% usage so theoretically
they should be as same fast.

-- 
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:[~2013-03-04 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04 14:01 bugzilla-daemon [this message]
2013-03-26  7:43 ` [Bug 54761] Variable cpu frequency causes to loose performance bugzilla-daemon
2013-03-26  9:08 ` bugzilla-daemon
2013-03-26  9:15 ` bugzilla-daemon
2013-03-26  9:41 ` bugzilla-daemon
2013-03-26 13:24 ` bugzilla-daemon
2013-04-18  9:12 ` 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-54761-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 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.