From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] [RFC] pselect01: Tune thresholds
Date: Mon, 22 May 2017 17:15:55 +0200 [thread overview]
Message-ID: <20170522151555.GD11771@rei.lan> (raw)
In-Reply-To: <297220533.19197153.1495465050258.JavaMail.zimbra@redhat.com>
Hi!
> > New measure script attached, now with gnuplot frequency graphs.
> >
> > Can you, pretty please run that on the slow x86 machine, so that we know
> > if the failure is caused by a few outliners of if the measured times are
> > simply skeewed there?
>
> Attached.
Hmm, strange, it looks like for 100us we got more or less all samples
close to 160us but for 500us half of the samples are close to 560us and
about 400 is more than 1000us, that does not look right. I wonder what
happens there. And the same for the rest of the measurements everything
but 100us sleeps has two peaks that are more or less 500us apart. So far
my machines, even VMs, had one peak and some outliners.
Can you try to rerun the test with a realtime priority?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-05-22 15:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 14:16 [LTP] [PATCH v2] [RFC] pselect01: Tune thresholds Cyril Hrubis
2017-05-15 10:03 ` Jan Stancek
2017-05-15 10:20 ` Xiao Yang
2017-05-15 13:15 ` Jan Stancek
2017-05-15 13:23 ` Cyril Hrubis
2017-05-15 12:36 ` Cyril Hrubis
2017-05-15 13:00 ` Jan Stancek
2017-05-15 13:13 ` Cyril Hrubis
2017-05-15 13:16 ` Jan Stancek
2017-05-22 8:39 ` Jan Stancek
2017-05-22 12:04 ` Cyril Hrubis
2017-05-22 13:37 ` Jan Stancek
2017-05-22 13:19 ` Cyril Hrubis
2017-05-22 14:57 ` Jan Stancek
2017-05-22 15:15 ` Cyril Hrubis [this message]
2017-05-23 7:54 ` Jan Stancek
2017-05-23 9:16 ` Cyril Hrubis
2017-05-23 9:45 ` Jan Stancek
2017-06-02 12:48 ` Jan Stancek
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=20170522151555.GD11771@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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