Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: Confusing Performance Numbers
Date: Wed, 13 Nov 2013 15:02:10 +0100	[thread overview]
Message-ID: <lyppq4z9gd.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <1384270308.6460.11.camel@ted> (Richard Purdie's message of "Tue,  12 Nov 2013 15:31:48 +0000")

Richard Purdie
<richard.purdie-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
writes:

> I had some ideas I decided to test out. Specifically:
> Its very hard to figure out what in these tests might be noise and what
> if anything was a real gain (other than the disk usage improvements). I
> suspect the hardlinking patch may be worthwhile, the other two are
> perhaps not useful.

fwiw, we record performance data as part of our normal build process and
it should be possible to compare these statistics.  Results are e.g.

             https://www.cvg.de/people/ensc/metrics.txt.gz
             https://www.cvg.de/people/ensc/metrics.html

(there is much room to improve the visualization; a new colleague just
started to work on it).  Relevant changes/classes are

  https://www.cvg.de/people/ensc/metrics.py
  https://www.cvg.de/people/ensc/elito-metrics.bbclass
  https://www.cvg.de/people/ensc/0008-build.py-fire-TaskFailed-with-same-environment-as-Ta.patch




Enrico


      parent reply	other threads:[~2013-11-13 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 15:31 Confusing Performance Numbers Richard Purdie
2013-11-12 23:33 ` Phil Blundell
2013-11-13 14:02 ` Enrico Scholz [this message]

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=lyppq4z9gd.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox