From: Koen Kooi <koen@dominion.thruhere.net>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Build time data
Date: Thu, 19 Apr 2012 12:00:54 +0200 [thread overview]
Message-ID: <A1812F33-640B-413F-8E3A-0B3784A9630C@dominion.thruhere.net> (raw)
In-Reply-To: <1334306723.7309.54.camel@ted>
Op 13 apr. 2012, om 10:45 heeft Richard Purdie het volgende geschreven:
> On Thu, 2012-04-12 at 07:34 -0700, Darren Hart wrote:
>>
>> On 04/12/2012 07:08 AM, Björn Stenberg wrote:
>>> Darren Hart wrote:
>>>> /dev/md0 /build ext4
>>>> noauto,noatime,nodiratime,commit=6000
>>>
>>> A minor detail: 'nodiratime' is a subset of 'noatime', so there is no
>>> need to specify both.
>>
>> Excellent, thanks for the tip.
>
> Note the key here is that for a system with large amounts of memory, you
> can effectively keep the build in memory due to the long commit time.
>
> All the tests I've done show we are not IO bound anyway.
Consider this scenario:
OS disk on spinning rust (sda1, /)
BUILDDIR on spinning rust (sdb1, /OE)
WORKDIR on SSD (sdc1, /OE/build/tmp/work)
SD card in USB reader (sde1)
When I do the following during a build all CPUs will enter IO wait and the build grinds to a halt:
cd /media ; xz -d -c foo.img.xz | pv -s 3488M > /dev/sde
That only touches the OS disk and the SD card, but for some reason the 3.2.8 kernel stops IO to the OE disks as well. do_patch for my kernel recipe has been taking more than an hour now, it usually completes in less than 5 minutes (a few hundred patches applied with a custom patcher, git-am).
regards,
Koen
next prev parent reply other threads:[~2012-04-19 10:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 20:42 Build time data Chris Tapp
2012-04-11 21:19 ` Autif Khan
2012-04-11 21:38 ` Bob Cochran
2012-04-12 0:30 ` Darren Hart
2012-04-12 0:43 ` Osier-mixon, Jeffrey
2012-04-12 4:39 ` Bob Cochran
2012-04-12 7:10 ` Darren Hart
2012-04-12 7:35 ` Joshua Immanuel
2012-04-12 8:00 ` Martin Jansa
2012-04-12 9:36 ` Joshua Immanuel
2012-04-12 14:12 ` Darren Hart
2012-04-12 23:37 ` Flanagan, Elizabeth
2012-04-13 5:51 ` Martin Jansa
2012-04-13 6:08 ` Darren Hart
2012-04-13 6:38 ` Martin Jansa
2012-04-13 7:24 ` Wolfgang Denk
2012-04-17 15:29 ` Martin Jansa
2012-04-12 14:08 ` Björn Stenberg
2012-04-12 14:34 ` Darren Hart
2012-04-12 22:43 ` Chris Tapp
2012-04-12 22:56 ` Darren Hart
2012-04-18 19:41 ` Chris Tapp
2012-04-18 20:27 ` Chris Tapp
2012-04-18 20:55 ` Darren Hart
2012-04-19 22:39 ` Chris Tapp
2012-04-13 8:45 ` Richard Purdie
2012-04-19 10:00 ` Koen Kooi [this message]
2012-04-19 12:48 ` Joshua Immanuel
2012-04-19 12:52 ` Richard Purdie
2012-04-19 13:47 ` Samuel Stirtzel
2012-04-13 8:47 ` Björn Stenberg
2012-04-13 14:41 ` Darren Hart
2012-04-19 7:24 ` Björn Stenberg
2012-04-19 14:11 ` Darren Hart
2012-04-13 9:56 ` Tomas Frydrych
2012-04-13 10:23 ` Koen Kooi
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=A1812F33-640B-413F-8E3A-0B3784A9630C@dominion.thruhere.net \
--to=koen@dominion.thruhere.net \
--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.