Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:15:09 +0200	[thread overview]
Message-ID: <20120906161509.2f5fc914@skate> (raw)
In-Reply-To: <1346940241.6846.YahooMailNeo@web110707.mail.gq1.yahoo.com>

Le Thu, 6 Sep 2012 07:04:01 -0700 (PDT),
Vimal Menon <vimalmenon@yahoo.com> a ?crit :

> I happened to download and install buildroot (default 2012.05), while
> checking the compiled image, I saw that python runs very slow. for eg:
> 
> On a standard linux, Python 2.7.2 complied with glibc
> 
> #time python -c "print 'hello world'" 
> 
> hello world
> 
> real??? 0m0.077s
> user??? 0m0.068s
> sys???? 0m0.009s
> 
> and the same command ran on the same machine with the buildroot
> compiled image (not via qemu, but with the image booted through
> grub), python takes a lot more time
> 
> #time python -c "print 'hello world'" 
> 
> hello world
> real??? 0m 0.28s
> user??? 0m 0.26s
> sys???? 0m 0.01s
> 
> Why would there be such a huge difference? What might I have done
> wrong? Has anybody of you come across such a situation?

You're not running the C library (by default, Buildroot uses uClibc),
and maybe you're not using the same optimization flags as well.

Try to build a Buildroot system based on glibc, and use the appropriate
optimization flags, maybe it will improve the situation.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-09-06 14:15 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 [this message]
2012-09-06 14:27   ` Vimal Menon
2012-09-06 14:34     ` Thomas Petazzoni
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=20120906161509.2f5fc914@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