From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Improving build performance (on slow storage)
Date: Thu, 13 Jun 2019 16:17:06 +0100 [thread overview]
Message-ID: <9E522EE9-4BCC-4EBD-ADBD-8B6FAC510FB3@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Hello,
I just wanted to post you an update about the build system which we have recently merged.
The whole build process is primarily CPU bound and secondarily IO bound. Some builders have by definition slow storage (the ARM SBCs for example), but also for other reason it does not make sense to run the build on persistent storage. We can keep it in RAM instead which makes accessing files a lot faster and saves write cycles on the media.
Therefore, the make.sh build script is mounting /usr/src in the build environment as a ramdisk. All source will be extracted there and the build will be performed. After the build is done, the whole ramdisk will be destroyed again.
This feature is automatically enabled on all build systems which have 4GB of RAM or more. You can manually disable it with the ENABLE_RAMDISK=off switch in .config.
I hope this brief email makes sense. If you have any questions, feel free to ask.
Best,
-Michael
next reply other threads:[~2019-06-13 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 15:17 Michael Tremer [this message]
2019-06-15 10:03 ` Matthias Fischer
2019-06-15 13:51 ` Michael Tremer
2019-06-15 14:12 ` Matthias Fischer
2019-09-17 16:18 ` Matthias Fischer
2019-09-17 20:30 ` Michael Tremer
2019-09-18 14:31 ` Arne Fitzenreiter
2019-09-18 16:42 ` Matthias Fischer
2019-09-18 16:42 ` Matthias Fischer
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=9E522EE9-4BCC-4EBD-ADBD-8B6FAC510FB3@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox