All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adrian Bunk" <bunk@stusta.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [yocto] thoughts on YP-friendly developer laptop?
Date: Mon, 14 Jun 2021 16:24:00 +0300	[thread overview]
Message-ID: <20210614132400.GC5362@localhost> (raw)
In-Reply-To: <72e88753-bee4-a983-1c1-359ecc9855f1@crashcourse.ca>

On Mon, Jun 14, 2021 at 07:58:19AM -0400, Robert P. J. Day wrote:
> 
>   starting to think about a new laptop that will, among other things,
> do lots of OE/YP builds, and i'll start with this as the basis for a
> few questions about hard drives:
> 
> https://www.dell.com/en-ca/shop/gaming-laptops/g15-ryzen-edition-gaming-laptop/spd/g-series-15-5515-laptop/ng155515_sb_ps25e
> 
> while an SSD would be delightful, i'm concerned about how doing
> frequent 40-50G builds would wear out an SSD. so i was considering
> looking for something with a fast regular HD for the actual build
> directories, but room to put in an M.2 NVMe that would hold fairly
> static content, like the OS itself, all the layers, a local source
> mirror and so on.
> 
> am i overthinking this? anyone have a laptop setup that is smokin'
> fast (yeah, 8 core AMD ryzen :-),

When using a laptop with only 16 GB RAM to build with 8 or 16 threads,
on what drive will the heavily used large swap partition be?

gcc loves to use > 2 GB RAM for non-trivial C++ code,
with 16 threads I'd recommend 64 GB RAM.

> and a dual drive layout that seems
> to work well with lots and lots of OE builds?

Ask for the specs of the SSD and do the math.

E.g. 150 TBW / 50 GB/build = 3000 builds

If you are building from scratch so often that the resulting number
is a worry, I'd rather buy 128 GB RAM and use a tmpfs instead of
creating a spinning rust bottleneck.

> rday

cu
Adrian

      parent reply	other threads:[~2021-06-14 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 11:58 thoughts on YP-friendly developer laptop? Robert P. J. Day
2021-06-14 12:32 ` [yocto] " Jack Mitchell
2021-06-14 13:24 ` Adrian Bunk [this message]

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=20210614132400.GC5362@localhost \
    --to=bunk@stusta.de \
    --cc=rpjday@crashcourse.ca \
    --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.