All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: OpenEmbedded <openembedded-core@lists.openembedded.org>
Subject: Re: rm_work + pybootchart enhancements
Date: Thu, 22 Sep 2016 14:52:51 +0200	[thread overview]
Message-ID: <1474548771.16834.100.camel@intel.com> (raw)
In-Reply-To: <20160921160854.GB2633@jama>

On Wed, 2016-09-21 at 18:08 +0200, Martin Jansa wrote:
> On Wed, Sep 21, 2016 at 05:39:02PM +0200, Patrick Ohly wrote:
> > Test script attached. I only ran this once, so I can't vouch that the
> > numbers are stable. I remember reading about a benchmark wrapper which
> > can run such a test script multiple times and then will automatically
> > merge the output of all runs together, adding min/max/average/deviation,
> > but couldn't find the tool again. Does anyone know which tool does that?
> 
> it's in oe-core:
> ./scripts/contrib/bb-perf/bb-matrix-plot.sh
> ./scripts/contrib/bb-perf/bb-matrix.sh
> 
> ...

That's bitbake specific. What I was remembering is something generic
that works for anything that prints test results on stdout. Perhaps I
was dreaming ;-}

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2016-09-22 12:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 15:39 rm_work + pybootchart enhancements Patrick Ohly
2016-09-21 16:08 ` Martin Jansa
2016-09-22 12:52   ` Patrick Ohly [this message]
2016-09-22 17:37     ` Christopher Larson
2016-09-23  5:51       ` Patrick Ohly
2016-09-23  6:01 ` Patrick Ohly

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=1474548771.16834.100.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.