All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Xianghua Xiao <xiaoxianghua@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: building and using yocto 1.1
Date: Fri, 28 Oct 2011 11:23:36 -0500	[thread overview]
Message-ID: <4EAAD708.5030909@windriver.com> (raw)
In-Reply-To: <CAP7cwttTXcGySrqmKvv+7saHFyF0xuUczY8h5693f232RCA_Sg@mail.gmail.com>

On 10/28/11 11:13 AM, Xianghua Xiao wrote:
> core2duo E7200 2.53Ghz  4GB 500GB
> 
> 1 thread 1 parallel due to past experience I had from the
> past(parallel make did not work well reliably)

It is a goal of the Yocto Project (and Open Embedded) that parallel building is
full supported, and any identified bugs are fixed quickly.

Enable parallel builds and your performance will be significantly better.

If you have hyperthreading enabled, and setup a 4/4 parallel build.  I would
expect about a 4-5 hour build time.  (May be faster)

--Mark

> thanks,
> xianghua
> 
> 
> On Fri, Oct 28, 2011 at 9:45 AM, Mark Hatle <mark.hatle@windriver.com> wrote:
>> What machine are you using (amount of ram, disk space, and cpu cores)?
>>
>> What configuration did you set for parallel builds?
>>
>> I can build 1.1 on an 8 core i7 system w/ 8 GB of ram, set with parallel
>> settings of 8 thread and 8 parallel make jobs, in about 100 minutes (or less).
>>
>> --Mark
>>
>> On 10/28/11 9:20 AM, Xianghua Xiao wrote:
>>> when I built 1.0 out of the box, it took 7 hours.
>>> on the same machine/network, yocto 1.1 took a full 12 hours, not sure
>>> what happened to cause this nearly doubled build time.
>>>
>>> after the default build(bitbake core-image-sato), I run 'runqemu
>>> qemux86', click on 'tasks', try to add a new task, however my input is
>>> shown non-english, or garbage on screen, which I have seen the same
>>> issue on yocto1.0 release as well. this is a 10.04 ubuntu 64bit
>>> machine.
>>>
>>> don't know what to say about it, just my OOB(out-of-box) experience
>>>
>>> xianghua
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>



  parent reply	other threads:[~2011-10-28 16:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28 14:20 building and using yocto 1.1 Xianghua Xiao
2011-10-28 14:45 ` Mark Hatle
2011-10-28 15:07   ` Xu, Jiajun
2011-10-28 16:13   ` Xianghua Xiao
2011-10-28 16:20     ` Xianghua Xiao
2011-10-28 16:45       ` Joshua Lock
2011-10-28 17:17         ` Xianghua Xiao
2011-10-28 16:23     ` Mark Hatle [this message]
2011-10-28 16:39       ` Xianghua Xiao
2011-10-28 16:47         ` Joshua Lock

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=4EAAD708.5030909@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=xiaoxianghua@gmail.com \
    --cc=yocto@yoctoproject.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.