From: Robert Yang <liezhi.yang@windriver.com>
To: <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/8] python: Run pybench once for optimisation task in pgo
Date: Thu, 6 Sep 2018 16:22:53 +0800 [thread overview]
Message-ID: <0b2eb458-7af6-3f7f-396c-461bb2bdb54c@windriver.com> (raw)
In-Reply-To: <cea8be2755a95002fb28718121baa756a7e4f668.camel@linuxfoundation.org>
On 09/06/2018 04:17 PM, richard.purdie@linuxfoundation.org wrote:
> On Thu, 2018-09-06 at 16:15 +0800, Robert Yang wrote:
>> What's the fault if I don't run it, please ? This is very slow, here
>> are some rough thoughts to speed it up:
>>
>> 1) Make it optional to run, and default to no if there isn't any
>> faults without running it.
>
> Without running it, python is not profile optimised and runs slower.
>
>> 2) Use qemu-kvm to run the tests if qemu kvm has been setup (I tried
>> it, it can
>> reduce form 12m -> 4m, saved 8 mins:
>> * Without kvm
>> $ bitbake python3 -ccleansstate && time bitbake python3
>> real 12m28.070s
>> user 0m1.316s
>> sys 0m0.184s
>>
>> * With kvm:
>> real 3m53.781s
>> user 0m1.080s
>> sys 0m0.220s
>>
>> We may need a oe-core/scripts/qemu-kvm-check to check strictly
>> whether kvm
>> can be used or not.
>>
>> Please feel free to give your comments.
>
> Ross has some patches coming in this area which should improve things a
> lot so I'd suggest we wait for those. I merged the n10 -> n1 change
> simply because it was an easy fix to same some time whilst the other
> patches a debugged.
Sounds great, thanks.
// Robert
>
> Cheers,
>
> Richard
>
prev parent reply other threads:[~2018-09-06 8:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 16:52 [PATCH 1/8] python: Run pybench once for optimisation task in pgo Richard Purdie
2018-09-05 16:52 ` [PATCH 2/8] os-release: fix to install in the expected location Richard Purdie
2018-09-05 17:16 ` Andre McCurdy
2018-09-05 17:20 ` richard.purdie
2018-09-05 16:52 ` [PATCH 3/8] gcc: Merge two related patches together Richard Purdie
2018-09-05 16:52 ` [PATCH 4/8] binutils: Fix variable conflict Richard Purdie
2018-09-05 20:52 ` Khem Raj
2018-09-05 16:52 ` [PATCH 5/8] populate_base_sdk: Stop running gcc --version all the time Richard Purdie
2018-09-05 16:52 ` [PATCH 6/8] maintainers: Add entry for fribidi Richard Purdie
2018-09-05 16:52 ` [PATCH 7/8] busybox: Put klogd/syslogd alternative links in syslog package Richard Purdie
2018-09-06 2:11 ` ChenQi
2018-09-06 8:19 ` richard.purdie
2018-09-06 9:04 ` ChenQi
2018-09-06 22:05 ` richard.purdie
2018-09-06 22:51 ` Richard Purdie
2018-09-07 14:07 ` Mark Hatle
2018-09-05 16:52 ` [PATCH 8/8] busybox: Sync arch and link locations with coreutils Richard Purdie
2018-09-06 8:15 ` [PATCH 1/8] python: Run pybench once for optimisation task in pgo Robert Yang
2018-09-06 8:17 ` richard.purdie
2018-09-06 8:22 ` Robert Yang [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=0b2eb458-7af6-3f7f-396c-461bb2bdb54c@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox