mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
	peterz@infradead.org, mingo@kernel.org,
	linux-kernel@vger.kernel.org, rjw@rjwysocki.net
Cc: juri.lelli@redhat.com, Morten.Rasmussen@arm.com,
	viresh.kumar@linaro.org, valentin.schneider@arm.com
Subject: Re: [PATCH 0/4 v4] sched/rt: track rt rq utilization
Date: Sun, 15 Apr 2018 13:56:53 +0200	[thread overview]
Message-ID: <08e478a1-e1ff-4547-b95b-2975bc5c5b5d@arm.com> (raw)
In-Reply-To: <1521199541-15308-1-git-send-email-vincent.guittot@linaro.org>

On 03/16/2018 12:25 PM, Vincent Guittot wrote:

[...]

> For a 15 seconds long test on a hikey 6220 (octo core cortex A53 platfrom),
> the cpufreq statistics outputs (stats are reset just before the test) :
> $ cat /sys/devices/system/cpu/cpufreq/policy0/stats/total_trans
> without patchset : 1230
> with patchset : 14
> 
> If we replace the cfs thread of rt-app by a sysbench cpu test, we can see
> performance improvements:
> 
> - Without patchset :
> Test execution summary:
>      total time:                          15.0009s
>      total number of events:              4903
>      total time taken by event execution: 14.9972
>      per-request statistics:
>           min:                                  1.23ms
>           avg:                                  3.06ms
>           max:                                 13.16ms
>           approx.  95 percentile:              12.73ms
> 
> Threads fairness:
>      events (avg/stddev):           4903.0000/0.00
>      execution time (avg/stddev):   14.9972/0.00
> 
> - With patchset:
> Test execution summary:
>      total time:                          15.0014s
>      total number of events:              7694
>      total time taken by event execution: 14.9979
>      per-request statistics:
>           min:                                  1.23ms
>           avg:                                  1.95ms
>           max:                                 10.49ms
>           approx.  95 percentile:              10.39ms
> 
> Threads fairness:
>      events (avg/stddev):           7694.0000/0.00
>      execution time (avg/stddev):   14.9979/0.00
> 
> The performance improvement is 56% for this use case.

How do you get this number? Normally we use the 'total time' value.

[...]

  parent reply	other threads:[~2018-04-15 11:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 11:25 Vincent Guittot
2018-03-16 11:25 ` [PATCH 1/4 v4] sched/pelt: Move pelt related code in a dedicated file Vincent Guittot
2018-04-15 11:58   ` Dietmar Eggemann
2018-04-15 12:16     ` Vincent Guittot
2018-04-15 13:27       ` Dietmar Eggemann
2018-04-15 11:58   ` Dietmar Eggemann
2018-03-16 11:25 ` [PATCH 2/4 v4] sched/rt: add rt_rq utilization tracking Vincent Guittot
2018-04-14 10:05   ` Peter Zijlstra
2018-04-14 11:29     ` Vincent Guittot
2018-03-16 11:25 ` [PATCH 3/4 v4] cpufreq/schedutil: add rt " Vincent Guittot
2018-03-16 11:25 ` [PATCH 4/4 v4] sched/nohz: monitor rt utilization Vincent Guittot
2018-04-14 10:07 ` [PATCH 0/4 v4] sched/rt: track rt rq utilization Peter Zijlstra
2018-04-14 11:42   ` Vincent Guittot
2018-04-15 11:56 ` Dietmar Eggemann [this message]
2018-04-15 12:00   ` Vincent Guittot

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=08e478a1-e1ff-4547-b95b-2975bc5c5b5d@arm.com \
    --to=dietmar.eggemann@arm.com \
    --cc=Morten.Rasmussen@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=valentin.schneider@arm.com \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.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

Powered by JetHome