From: Phil Blundell <pb@pbcl.net>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Prelink problems -- need help!
Date: Mon, 26 Oct 2015 21:18:19 +0000 [thread overview]
Message-ID: <1445894299.6900.8.camel@pbcl.net> (raw)
In-Reply-To: <562E5AF1.3080807@windriver.com>
On Mon, 2015-10-26 at 11:55 -0500, Mark Hatle wrote:
> -last- time I got concrete numbers on a complex boot process. It was on the
> order of 1-5% boot time.. and a fairly large number of pages saved.. (which
> reduced fragmentation as well as saved memory.)
I'm slightly surprised at the 5% figure. Martin Jansa posted some
statistics in another thread earlier today which showed an improvement
from prelink of just under 0.5% (0.24 seconds saved out of 49.51 seconds
total) and that's more like what I would have expected. What sort of
binaries were you running on the system you measured?
I also don't entirely understand the fragmentation argument. We're not
talking about a no-mmu configuration here, are we?
p.
next prev parent reply other threads:[~2015-10-26 21:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 14:28 Prelink problems -- need help! Mark Hatle
2015-10-26 16:10 ` Phil Blundell
2015-10-26 16:45 ` Mark Hatle
2015-10-26 16:50 ` Phil Blundell
2015-10-26 16:55 ` Mark Hatle
2015-10-26 21:18 ` Phil Blundell [this message]
2015-10-26 21:35 ` Mark Hatle
2015-10-29 18:32 ` Khem Raj
2015-10-29 18:41 ` Mark Hatle
2015-10-27 0:40 ` Mark Hatle
2015-10-30 3:50 ` Prelink status Mark Hatle
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=1445894299.6900.8.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=mark.hatle@windriver.com \
--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 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.