From: John Kacur <jkacur@redhat.com>
To: Piotr Gregor <piotrgregor@rsyncme.org>
Cc: Clark Williams <williams@redhat.com>,
Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: Calculate average latencies on the fly
Date: Mon, 21 Nov 2016 19:32:41 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.20.1611211928160.8986@riemann> (raw)
In-Reply-To: <CAK+oA4UTKEazEFZ9+H6xWT7yNw50LNLe+e_DpfwKFvnwaYe1xQ@mail.gmail.com>
On Sat, 19 Nov 2016, Piotr Gregor wrote:
> Hi John, Clark,
>
> Recently I observed jitter of > 100 000 during tests of virtualized system.
> In that case 30 years would change into 0.3 year which is not as much.
> The jitter depends on the hardware/software you test, what if someone
> deliberately wishes to measure jitter of more than this or he is just
> out of luck and gets huge values?
> Also, the limit will change if the type of average changes, but if it
> is calculated in the way I proposed, it will always work.
> Apart from this, since the benign possibility exists - why not to fix this
> if the fix is easy.
>
I already explained why. Everytime you do a floating point long division
you are potentially accumulating small errors. Something is terribly
wrong if you are getting a diff of greater than 100,000, if that really
is true you need to fix it right away instead of run cyclictest for a
long period of time.
John>
next prev parent reply other threads:[~2016-11-21 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 10:00 Calculate average latencies on the fly Piotr Gregor
2016-11-14 11:50 ` Piotr Gregor
2016-11-14 15:42 ` Mathieu Poirier
2016-11-14 16:11 ` Piotr Gregor
2016-11-14 16:58 ` Clark Williams
2016-11-16 14:47 ` John Kacur
2016-11-19 23:27 ` Piotr Gregor
2016-11-20 5:03 ` Tracy Smith
2016-11-21 18:32 ` John Kacur [this message]
[not found] ` <CAChUvXOj_D2N3o7BoEUjt1A1O0fXZnvGSz5ba=O55h12ns___A@mail.gmail.com>
2016-11-22 15:43 ` John Kacur
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=alpine.LFD.2.20.1611211928160.8986@riemann \
--to=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=piotrgregor@rsyncme.org \
--cc=williams@redhat.com \
/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.