From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] python: Add performance patches from upstream 2.7 branch
Date: Wed, 17 Jun 2015 22:03:23 +0100 [thread overview]
Message-ID: <1434575003.14710.38.camel@linuxfoundation.org> (raw)
In-Reply-To: <1434546648.14710.25.camel@linuxfoundation.org>
On Wed, 2015-06-17 at 14:10 +0100, Richard Purdie wrote:
> These performance patches result in about a 25% speed up of our parsing
> speed with bitbake. They're already applied in 1.7 upstream and backported
> from 3.X so worth applying for 2.7 too.
Sadly, this was too good to be true. I'd messed up the test environment
and the 25% is Ubuntu's python verses the one from OE. Ubuntu's uses PGO
whereas ours does not which is likely where the speed comes from. The
patches in this series do give a small speedup, but its more like
0.5-1%. Shows that PGO is likely worth investigating further though.
Cheers,
Richard
next prev parent reply other threads:[~2015-06-17 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 13:10 [PATCH] python: Add performance patches from upstream 2.7 branch Richard Purdie
2015-06-17 21:03 ` Richard Purdie [this message]
2015-08-16 8:47 ` Khem Raj
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=1434575003.14710.38.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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.