From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Python running very slow with buildroot 2012.05
Date: Thu, 06 Sep 2012 11:40:39 -0300 [thread overview]
Message-ID: <5048B5E7.7050002@zacarias.com.ar> (raw)
In-Reply-To: <20120906163440.69c585eb@skate>
On 09/06/12 11:34, Thomas Petazzoni wrote:
> Is is reproducible even after the first run? Are you running the same
> kernel, with the same configuration? Your two environments are really
> different, so it's very difficult to make correct comparisons and draw
> conclusions from them.
Exactly where i was going to point to.
He's basically measuring startup time, not a benchmark per se.
Also if, say, the main system is already running something with the
exact same glibc it's already preloaded, whereas if it's the first/only
thing uclibc-based it gets all the penalties, even after the first run.
Regards.
next prev parent reply other threads:[~2012-09-06 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 14:04 [Buildroot] Python running very slow with buildroot 2012.05 Vimal Menon
2012-09-06 14:15 ` Thomas Petazzoni
2012-09-06 14:27 ` Vimal Menon
2012-09-06 14:34 ` Thomas Petazzoni
2012-09-06 14:40 ` Gustavo Zacarias [this message]
2012-09-06 15:11 ` Thomas Petazzoni
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=5048B5E7.7050002@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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.