From: 杨同峰 <yangtf@envision.com.cn>
To: openembedded-devel@lists.openembedded.org
Subject: I hava an idea to Make OpenEmbedded Run Faster
Date: Mon, 27 Aug 2007 11:48:27 +0800 [thread overview]
Message-ID: <1188186507.2137.17.camel@localhost.localdomain> (raw)
EveryOne:
By two week of using OE , I hava notice that task was topology
sort to a queue .and Run Task One By One.
draw on the experience of Design of CPU . we can make a multiply thread
run of it !
I notice that the biggest bottleneck of OE is do_fetch . then we
can use a mutiply thread downloader instead of wget
And about task schedule ,use method like this:
bb_No1 do_fetch do_patch do_configure do_build do_install
bb_No2 do_fetch do_patch do_configure
do_build do_install
bb_No3 do_fetch do_patch
do_configure do_build do_install
bb_No4
do_fetch .......
Idea 1 : focus on download one file one time ,and make it more
fast use mutiply thread downloader
Idea 2 : make 0ther task of bb files to run asynchronously
Idea 3 : deal with task topology more carefully to make sure
that the bb file that was dependend was finish before
this one start to do_patch (Notice : not before
do_fetch )
Idea 4 : If topology can't make sure Idea 3 ,we must tell OE how
and when to wait
If the Idea can come true ,The speed can go 3 times faster then
now
Tongfeng Yang
2007-8-27
next reply other threads:[~2007-08-27 3:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 3:48 杨同峰 [this message]
2007-08-27 4:04 ` I hava an idea to Make OpenEmbedded Run Faster Justin Patrin
2007-08-27 4:23 ` 杨同峰
2007-08-27 4:40 ` 杨同峰
2007-08-27 5:51 ` Justin Patrin
2007-08-27 6:08 ` 杨同峰
2007-08-27 6:34 ` 杨同峰
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=1188186507.2137.17.camel@localhost.localdomain \
--to=yangtf@envision.com.cn \
--cc=openembedded-devel@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.