All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Martin Jansa <Martin.Jansa@gmail.com>
Cc: Yoann Congal <yoann.congal@smile.fr>,
	MOHAMMED HASSAN <hassanchattarki@gmail.com>,
	yocto@lists.yoctoproject.org
Subject: Re: [yocto] Memory requirements for building images with different architectures
Date: Fri, 8 Sep 2023 09:20:34 +0200	[thread overview]
Message-ID: <20230908072034c8e150e6@mail.local> (raw)
In-Reply-To: <CA+chaQdiOTNYTsrhPzbT=9aB3fT9Mo=DoorvNm4Bay2ioRTsdA@mail.gmail.com>

On 08/09/2023 09:06:39+0200, Martin Jansa wrote:
> On Fri, Sep 8, 2023 at 8:42 AM Yoann Congal <yoann.congal@smile.fr> wrote:
> 
> > Hi!
> > Le ven. 8 sept. 2023 à 08:01, MOHAMMED HASSAN <hassanchattarki@gmail.com>
> > a écrit :
> >
> >> Right, you're not the only one!
> >> See
> >>
> >> https://docs.yoctoproject.org/ref-manual/system-requirements.html#minimum-free-disk-space
> >> and https://docs.yoctoproject.org/dev/dev-manual/disk-space.html
> >>
> >> I can use rm_work and remove all the build related files, however every
> >> subsequent build would take a lot more time to build. I want my builds to
> >> be as fast as possible. Do you have any suggestions to for faster builds
> >> while consuming less memory space.
> >>
> >
> > rm_work does not impact build time.
> >
> 
> That's not true, if only do_install task checksum changed, then without
> rm_work you can reuse existing do_compile and re-run just following tasks,
> while with rm_work it will need to rebuild from scratch (because
> do_populate_sysroot and do_package sstate archives won't be valid anymore)
> adding more wear to those NVME drives.
> 

Did you really have any wear related issues on SSD disks? The
autobuilders are churning a lot of builds and the disk are doing just
fine.



-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2023-09-08  7:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08  5:02 Memory requirements for building images with different architectures MOHAMMED HASSAN
2023-09-08  5:12 ` [yocto] " Michael Opdenacker
2023-09-08  6:01   ` MOHAMMED HASSAN
2023-09-08  6:41     ` [yocto] " Yoann CONGAL
2023-09-08  7:06       ` Martin Jansa
2023-09-08  7:18         ` MOHAMMED HASSAN
2023-09-08  7:21           ` [yocto] " Leon Woestenberg
2023-09-08  7:20         ` Alexandre Belloni [this message]
2023-09-08  8:15           ` Martin Jansa
2023-09-08  8:47             ` Leon Woestenberg
2023-09-08  8:51             ` Mikko Rapeli
2023-09-08 10:58               ` 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=20230908072034c8e150e6@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=Martin.Jansa@gmail.com \
    --cc=hassanchattarki@gmail.com \
    --cc=yoann.congal@smile.fr \
    --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.