All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v5.10-rc2-rt4
Date: Wed, 11 Nov 2020 19:39:01 +0100	[thread overview]
Message-ID: <20201111183901.GA23846@beryllium> (raw)
In-Reply-To: <20201109163143.tm5gjz77rr734lm5@linutronix.de>

Sorry for the late response, I had to reinstall my system after a FS
corruption...

On Mon, Nov 09, 2020 at 05:31:43PM +0100, Sebastian Andrzej Siewior wrote:
> > These test run only very short with hackbench as worlkload (5 minutes).
> > Though I running these tests now for more than year with v4.4-rt and
> > some times the newer -rt releases and I've never seen the latency
> > numbers above 200us unless something was broken. Given that 5 minutes is
> > not really long, I'll let those test run for longer to see if I get the
> > same results when they run for one hour.

- 5.9.0-rc8-rt12, ca 5h
  T: 0 (11626) P:80 C:15092432 Min:     17 Act:   34 Avg:   43 Max:     226

- 5.9.0-rc8-rt13, ca 1.5h
  T: 0 (24661) P:80 C:5581936 Min:     21 Act:   35 Avg:   45 Max:     250

- 5.9.0-rc8-rt14, ca 1h
  T: 0 (  942) P:80 C:6522320 Min:     20 Act:   27 Avg:   44 Max:     352

This matches with the 5 minutes runs. -rt13 was still okay and -rt14
is clearly worse.

> > 5.10.0-rc2-rt4 vs 5.10.0-rc2-rt4(lazy preemption disabled)
> >
> >   0_cyclicdeadline     t2-max-latency       pass/pass                274.00/     61.00     349.18%
>
> So the value went from 274us to 61us after disabling lazy-preempt?

Yes, that was all I changed. I want to redo this measurement. It
really looks a bit bogus. Though, one thing after the other :)

Daniel

  reply	other threads:[~2020-11-11 18:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 19:57 [ANNOUNCE] v5.10-rc2-rt4 Sebastian Andrzej Siewior
2020-11-04 10:38 ` Daniel Wagner
2020-11-04 10:46   ` Sebastian Andrzej Siewior
2020-11-04 11:19     ` Daniel Wagner
2020-11-04 12:47       ` Daniel Wagner
2020-11-04 13:09         ` Sebastian Andrzej Siewior
2020-11-04 16:06           ` Daniel Wagner
2020-11-06 10:54             ` Sebastian Andrzej Siewior
2020-11-06 16:14               ` Daniel Wagner
2020-11-09 12:47                 ` Sebastian Andrzej Siewior
2020-11-09 14:37                   ` Daniel Wagner
2020-11-09 16:31                     ` Sebastian Andrzej Siewior
2020-11-11 18:39                       ` Daniel Wagner [this message]
2020-11-10 18:05                     ` Sebastian Andrzej Siewior
2020-11-12 12:39                       ` Daniel Wagner
2020-11-12 13:54                         ` Sebastian Andrzej Siewior

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=20201111183901.GA23846@beryllium \
    --to=wagi@monom.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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.