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 17:11:22 +0200	[thread overview]
Message-ID: <20120906171122.40d2226e@skate> (raw)
In-Reply-To: <5048B5E7.7050002@zacarias.com.ar>

Le Thu, 06 Sep 2012 11:40:39 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :

> 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.

Aaah, good point. Most likely his Linux distro has gazillions of
programs already running, so most of the glibc code is already in
memory. If not parts of the Python interpreter code itself. While on
the Buildroot system, no Python code has been executed since boot, and
only a minimal set of userspace applications has been executed, so not
much of uClibc code is in memory.

But I would strongly suspect that the Linux distro is already running a
Python app somewhere, so the Python interpreter is in memory already.

Well, to conclude: you're comparing apples to oranges and you really
cannot draw any conclusion from your "benchmark".

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 15:11 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
2012-09-06 15:11         ` Thomas Petazzoni [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=20120906171122.40d2226e@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