All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Build time data
Date: Thu, 12 Apr 2012 23:08:19 -0700	[thread overview]
Message-ID: <4F87C2D3.8020805@linux.intel.com> (raw)
In-Reply-To: <20120413055150.GA3652@jama.jama.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/12/2012 10:51 PM, Martin Jansa wrote:

> And my system is very slow compared to yours, I've found my
> measurement of core-image-minimal-with-mtdutils around 95 mins 
> http://patchwork.openembedded.org/patch/17039/ but this was with
> Phenom II X4 965, 4GB RAM, RAID0 (3 SATA2 disks) for WORKDIR, RAID5
> (the same 3 SATA2 disks) BUILDDIR (raid as mdraid), now I have
> Bulldozer AMD FX(tm)-8120, 16GB RAM, still the same RAID0 but 
> different motherboard..

Why RAID5 for BUILDDIR? The write overhead of RAID5 is very high. The
savings RAID5 alots you is more significant with more disks, but with
3 disks it's only 1 disk better than RAID10, with a lot more overhead.

I spent some time outlining all this a while back:
http://www.dvhart.com/2011/03/qnap_ts419p_configuration_raid_levels_and_throughput/

Here's the relevant bit:

"RAID 5 distributes parity across all the drives in the array, this
parity calculation is both compute intensive and IO intensive. Every
write requires the parity calculation, and data must be written to
every drive."



- --
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPh8LTAAoJEKbMaAwKp364pa8H/A8BSudN/g7ixFmUTYMNGHlC
2+H59MgNHYWRYzNn9QvN6vyyfXzX7C00HUTQ4MQ3CmisTUza2tbJEdX9CpeIBQNg
Ny8iqyNNoInTFx2T1Yi2eA9Ytegtue9Ls+IcBRbpIbs6Zo1Qwzi6oemdPZN7g3YI
rH/NKALWIBt/Y/Dt2k0fz7WsQGYOuE/lYpL/CmukU7vNNEUAdOs7tZa5o1ZOQDuj
zGCwuVH9QwrDJEXNsMtjNY37aJeAgDMwSXjN0pKv1WQI9j47kYQQrrp2qKVQYhV1
x4QxJ5aOuV7BaS0Y7zYkNo9nv+yKPODt25s5L83k5vjbMhCvczmMJn3jupQuUhQ=
=3GDA
-----END PGP SIGNATURE-----


  reply	other threads:[~2012-04-13  6:08 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 [this message]
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
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=4F87C2D3.8020805@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=martin.jansa@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.