From: Erwin Rol <mailinglists@erwinrol.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Build speed ups
Date: Mon, 18 Sep 2017 14:33:50 +0200 [thread overview]
Message-ID: <3066dd20-9749-e43a-b338-52a5f57a916d@erwinrol.com> (raw)
Hey All,
first thanks for the replies on my Yocto mail.
Now I have a real PTXdist question;
What do you use to speed up your builds?
For example I use webkitgtk and that clips my 24 core Xeon at 100% for
like 30 minutes.
ccache doesn't really help by a first run, it even makes it worse. Also
I must build several versions and so the ccache hast to be massive or
else the cache is always just updating and before you can use it it is
flushed from it already.
So get faster hardware? Of course one could get a >100k euro multi CPU
system, but I don't think that is the most economic choice.
Distributed CC (distcc/icecc) seem a possibly to scale up things in
smaller steps (ad cheap compile server one by one) Sadly I don't have
any experience with it, but it is something I want to look into.
PTXDist's -j functionality I can not use for all my builds, for example
I am stuck on kernel 3.1.10 (thanks nVidia), which means I am stuck on a
older systemd and can't use gcc 5.4 etc. So I am stuck at a rather old
ptxdist, and never got to try the -j stuff. (But with the webkitgtk
example it won't help much, the CPU is at 100% already)
So what do ppl do to make things faster ? I would really like to hear
other ppls experiences with large builds.
- Erwin
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2017-09-18 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 12:33 Erwin Rol [this message]
2017-09-18 13:43 ` Alexander Dahl
2017-09-18 17:14 ` Root
2017-09-19 4:45 ` Ulrich Ölmann
2017-09-19 6:42 ` Schenk, Gavin
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=3066dd20-9749-e43a-b338-52a5f57a916d@erwinrol.com \
--to=mailinglists@erwinrol.com \
--cc=ptxdist@pengutronix.de \
/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