From: "Adrian Bunk" <bunk@stusta.de>
To: Jean-Marie Lemetayer <jean-marie.lemetayer@savoirfairelinux.com>,
Paul Barker <pbarker@konsulko.com>,
Mikko Rapeli <mikko.rapeli@bmw.de>,
oliver westermann <oliver.westermann@cognex.com>,
yocto@lists.yoctoproject.org,
embedded-discuss <embedded-discuss@lists.savoirfairelinux.net>
Subject: Re: [yocto] What are the key factors for yocto build speed?
Date: Wed, 18 Mar 2020 16:49:06 +0200 [thread overview]
Message-ID: <20200318144906.GC23112@localhost> (raw)
In-Reply-To: <251912923.167286.1584540746314.JavaMail.zimbra@savoirfairelinux.com>
On Wed, Mar 18, 2020 at 10:12:26AM -0400, Jean-Marie Lemetayer wrote:
>...
> For example one of our build servers is using:
> - AMD Ryzen 9 3900X
>...
> - 32Go DDR4 3200 MHZ CL14
>...
> It is a really good price / build time ratio configuration.
Depends on what you are building.
Building non-trivial C++ code (e.g. webkitgtk) with 24 cores
but only 32 GB RAM will not work, for such code you need
more than 2 GB/core.
On Wed, Mar 18, 2020 at 05:52:37AM -0700, Oliver Westermann wrote:
>...
> Any suggestions what to put in that build to get the most out of it?
>
> Currently we're looking at a big Ryzen, 64G of RAM and one or multiple
> SSDs on a "consumer grade" board like the X570.
>...
I would buy 128 GB RAM to not run into problems due to lack of RAM,
and Linux will also automatically use unused RAM as disk cache.
As long as you aren't running out of RAM or disk space all that matters
is CPU speed, Ryzen 9 3950X with 128 GB RAM would be my choice unless
you are on a tight budget.
cu
Adrian
next prev parent reply other threads:[~2020-03-18 14:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 12:52 What are the key factors for yocto build speed? Oliver Westermann
2020-03-18 13:01 ` [yocto] " Mikko Rapeli
2020-03-18 13:29 ` Paul Barker
2020-03-18 14:12 ` Jean-Marie Lemetayer
2020-03-18 14:30 ` Alexander Kanavin
2020-03-18 14:49 ` Adrian Bunk [this message]
2020-03-18 15:09 ` Mike Looijmans
2020-03-18 15:51 ` Mikko Rapeli
2020-03-18 17:13 ` <EXT> " Srini
2020-03-18 17:47 ` David Stewart
2020-03-18 18:12 ` Yann Dirson
2020-03-18 18:15 ` Srini
2020-03-20 16:32 ` Philip Balister
2020-03-19 6:27 ` Mike Looijmans
2020-03-21 18:43 ` Oliver Westermann
2020-03-18 14:09 ` [yocto] " Mike Looijmans
2020-03-18 22:56 ` Ross Burton
2020-03-19 8:05 ` Mikko Rapeli
2020-03-19 11:04 ` Richard Purdie
2020-03-19 11:43 ` Mikko Rapeli
2020-03-19 11:48 ` Richard Purdie
2020-03-19 16:07 ` Mike Looijmans
2020-03-19 16:29 ` Yann Dirson
2020-03-19 17:04 ` Richard Purdie
2020-03-19 18:09 ` Yann Dirson
2020-03-19 17:21 ` Adrian Bunk
2020-03-19 17:26 ` Richard Purdie
2020-03-20 14:58 ` Mike Looijmans
2020-03-20 17:24 ` Adrian Bunk
2020-03-19 18:23 ` Khem Raj
[not found] ` <15FD6B43E957AFDB.13190@lists.yoctoproject.org>
2020-03-18 14:36 ` Mike Looijmans
2020-03-18 15:38 ` Martin Jansa
2020-03-21 18:39 ` Oliver Westermann
2020-03-21 18:58 ` [yocto] " Martin Jansa
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=20200318144906.GC23112@localhost \
--to=bunk@stusta.de \
--cc=embedded-discuss@lists.savoirfairelinux.net \
--cc=jean-marie.lemetayer@savoirfairelinux.com \
--cc=mikko.rapeli@bmw.de \
--cc=oliver.westermann@cognex.com \
--cc=pbarker@konsulko.com \
--cc=yocto@lists.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.