linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mahmood Naderan <mahmood.nt@gmail.com>
To: linux-perf-users@vger.kernel.org
Subject: Effect of sched_latency_ns
Date: Mon, 18 Apr 2022 11:24:08 +0200	[thread overview]
Message-ID: <CADa2P2VjP3GLMBvrQhD-mt1119r3UFNKVFVY3KRXuTLDvGV8yA@mail.gmail.com> (raw)

I would like to test the effect of latency_ns parameter on the
execution time of a program. The program is a 16-thread MM
implementation and the CPU is Ryzen with 8/16 (cores/threads). I also
have created a busy system with stress --cpu 16.

The default value of latency_ns is 24,000,000. If I use lower values,
the execution time gets longer. If I use larger values, the execution
time goes a little bit down. But the problem is when I use perf and
see the stats, they vary over multiple executions. This is expected
because of real hardware execution, but I am not able to figure out
the conclusion about the effect.

Example:

For 100,000

       142,696        context-switches
         1,625        cpu-migrations
        51,106        page-faults
  40.103996890 seconds time elapsed

For 24,000,000

        62,185        context-switches
           379        cpu-migrations
        52,929        page-faults
  19.424256128 seconds time elapsed

For 100,000,000

        63,646        context-switches
           513        cpu-migrations
        52,930        page-faults
  19.716886869 seconds time elapsed

        54,644        context-switches
           487        cpu-migrations
        52,894        page-faults
  16.788766277 seconds time elapsed



Any explanation about the effect? What should I expect?



Regards,
Mahmood

                 reply	other threads:[~2022-04-18  9:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CADa2P2VjP3GLMBvrQhD-mt1119r3UFNKVFVY3KRXuTLDvGV8yA@mail.gmail.com \
    --to=mahmood.nt@gmail.com \
    --cc=linux-perf-users@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;
as well as URLs for NNTP newsgroup(s).