From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Python running very slow with buildroot 2012.05
Date: Thu, 6 Sep 2012 16:34:40 +0200 [thread overview]
Message-ID: <20120906163440.69c585eb@skate> (raw)
In-Reply-To: <1346941637.60509.YahooMailNeo@web110712.mail.gq1.yahoo.com>
Hello,
Le Thu, 6 Sep 2012 07:27:17 -0700 (PDT),
Vimal Menon <vimalmenon@yahoo.com> a ?crit :
> I checked using default installations in both the environments, can
What do you mean by this? You're comparing the Python that has been
built by your distro with a certain compiler and certain optimization
flags, with the Python that has been built by Buildroot using a
different compiler, with different optimization flags.
> the difference between glibc and uClibc be so huge for python?
I don't know. Maybe the dynamic linker is slower, maybe some other
parts of the C library are slower, but I'm not sure, it needs
investigation.
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.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-09-06 14:34 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 [this message]
2012-09-06 14:40 ` Gustavo Zacarias
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=20120906163440.69c585eb@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox