From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Wolz, Troy" <Troy.Wolz@domain.hid>
Cc: Xenomai help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Xenomai Periodic Latency Spikes
Date: Thu, 17 May 2012 21:55:17 +0200 [thread overview]
Message-ID: <4FB557A5.5020202@domain.hid> (raw)
In-Reply-To: <E2AB2206BF591546A1931EA4E7A9FBC841502090@domain.hid>
On 05/17/2012 09:35 PM, Wolz, Troy wrote:
> In the attached plots, there appear to be very periodic spikes in
> latency. In the time between these spikes, the worst case latency is
> around 5 us. Is this to be expected? Is worst case latency typically
> periodic in nature?
>From the measurements I posted recently:
http://sisyphus.hd.free.fr/~gilles/core-3.2-latencies
It seems on higher-end machines, the probability decreases approximately
exponentially from the average latency to the max latency. So, every
latency smaller than the worst case latency has some probability to
happen, and happens from time to time.
On an atom 230 (which admittedly is not a such high end machine), the
average latency is less than 10us, but the maximum latency reaches 70us
when running with CONFIG_SMP.
The worst case latency you obtain on a machine without load, or over a
short period of time does not mean anything. If you are serious about
measuring the worst case latency, you have to do it over a long period
of time while running under load. We provide the "xeno-test" and
"dohell" scripts for that.
If your kernel is running with CONFIG_HZ set to 1000, the thing which
happens once every 1ms is the 8254 timer interrupt, on cpu 0 at least.
If you want to know what happens when the worst case latency is reached
you have to enable the I-pipe tracer and run the latency test with the
"-f" argument.
I am not saying that there is not a problem with your setup, but there
is nothing proving that in what you posted.
Please no:
- private mails
- html mails
- un-wrapped lines
- top-posting.
--
Gilles.
next prev parent reply other threads:[~2012-05-17 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 19:12 [Xenomai-help] Xenomai Periodic Latency Spikes Wolz, Troy
2012-05-17 19:16 ` Gilles Chanteperdrix
[not found] ` <E2AB2206BF591546A1931EA4E7A9FBC841502090@domain.hid>
2012-05-17 19:55 ` Gilles Chanteperdrix [this message]
2012-05-17 22:15 ` Gilles Chanteperdrix
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=4FB557A5.5020202@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Troy.Wolz@domain.hid \
--cc=xenomai@xenomai.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 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.