From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Paul <paul_c@tuxcnc.org>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Heads up: I-pipe patch status on ARM
Date: Sun, 29 Jul 2012 13:01:02 +0200 [thread overview]
Message-ID: <501517EE.7060904@xenomai.org> (raw)
In-Reply-To: <201207291044.22418.paul_c@tuxcnc.org>
On 07/29/2012 11:44 AM, Paul wrote:
> On Saturday 28 July 2012, Gilles Chanteperdrix wrote:
>> It does not look that bad. However, "dohell 3600" does not do much.
>> If you want to improve the latencies, use "-p 100" instead of "-p
>> 1000" ;-)
>
> Could try running a 'make j8 Image' in the kernel source tree. That
> would give the system a good run for my money.. However, dohell gives a
> baseline load that others could repeat (my excuse, and I'm sticking to
> it ;-p )
I agree, that is the reason we provide dohell. But what I meant is that
you should use the various options to add some load (-s adds network
trafic, -m adds some I/O, -l runs the whole LTP testsuite, which gives
the kernel the opportunity to try and perturb xenomai with many
differents paths in its code, and many different kinds of workload).
>
>> How do you get the fancy grid with gnuplot? We could add the option
>> to scripts/histo.gp. Note that I prefer to draw graphs with a log
>> scale, I find they are more meaningful, otherwise, you do not really
>> see how the graph ends.
>
> gnuplot> set grid
>
> The next set of plots, I'll use a log scale as you suggest.
We have been talking about this, but it would be nice to have a database
somewhere with the results of a latency runs (the file generated by
latency -g for instance), with some data attached (anything from a
simple free from string, to a complete database record with fields such
as linux version, I-pipe version, xenomai version, dohell command line),
and have a way to generate graphs from several such records. I guess
this could be done with a web application, using svg to avoid generating
the graphs on the server.
--
Gilles.
next prev parent reply other threads:[~2012-07-29 11:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 12:48 [Xenomai] Heads up: I-pipe patch status on ARM Gilles Chanteperdrix
2012-07-28 20:27 ` Paul
2012-07-28 20:41 ` Gilles Chanteperdrix
2012-07-29 9:44 ` Paul
2012-07-29 10:58 ` xenophile
2012-07-29 11:05 ` Gilles Chanteperdrix
2012-07-29 11:16 ` xenophile
2012-07-29 11:01 ` Gilles Chanteperdrix [this message]
2012-07-29 11:09 ` xenophile
2012-07-29 11:16 ` Gilles Chanteperdrix
2012-07-29 11:24 ` xenophile
2012-07-29 11:32 ` Gilles Chanteperdrix
2012-07-29 12:10 ` xenophile
2012-07-29 12:22 ` Gilles Chanteperdrix
2012-07-29 11:22 ` Gilles Chanteperdrix
2012-07-29 11:50 ` xenophile
2012-07-29 12:02 ` Gilles Chanteperdrix
2012-07-29 12:49 ` xenophile
2012-07-29 13:34 ` Gilles Chanteperdrix
2012-07-29 14:16 ` xenophile
2012-07-30 15:39 ` 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=501517EE.7060904@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=paul_c@tuxcnc.org \
--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.