public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: Tricks to speed up kernel builds
Date: Tue, 15 Sep 2009 20:35:50 -0600	[thread overview]
Message-ID: <200909152035.50814.tfjellstrom@shaw.ca> (raw)
In-Reply-To: <4AAF4ECD.5010401@pardus.org.tr>

On Tue September 15 2009, Ozan Çağlayan wrote:
> Hi,
> 
> I'd googled a lot about the $subject but couldn't find any detailed
> guide about it. So, the followings are what I understand from what I've
> found:
> 
> 1. Build inside a tmpfs to avoid I/O bottlenecks,
> 2. Use ccache,
> 3. Switch governor to performance if supported,
> 4. Pass -j to gnu make to parallelize the build process,
> 5. Don't build debug symbols a.k.a set CONFIG_DEBUG_INFO=n
> 6. There are a bunch of sched patches in tip which apparently improves
> things during kbuild
> 7. Distribute the work into the local network using icecream, distcc.
> 
> For the -j part, how many jobs should we pass to it? I've seen people
> passing
> 
> - NR_of_cores+1
> - NR_of_cores x 2 (I think that this is useful when there's 2 threads of
> execution per core like HyperThreading?)
> - 64, 128, etc. regardless of the number of cores (Is it really useful
> regardless of the CPU)
> 
> The curious question is *what build times can you get* with your typical
> systems using your speedup tricks (quad core, dual core, etc.) ? What
> are other tricks that I can use to even more speed up the build?
> 
> Do you really use icecream/distcc on your daily test builds?
> 
> How about nicing/ionicing make on an idle system? Will it make any
> difference?

I've only done a few compiles recently, and I only really use icecream and 
make -jX to speed up compile times.

I have a 4 node icecc cluster, three quad cores (one limited to 2 cores), and 
one dual core (limited to a single core), which gives 11 total cores I can 
distribute to, and I usually pass: make -j12

Any higher and I don't really see any speedups, any lower, same difference.

My last kernel compile (2.6.31-git4) took about 9 minutes.

> Thanks a lot
> Ozan Caglayan
> 
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


-- 
Thomas Fjellstrom
tfjellstrom@shaw.ca

  reply	other threads:[~2009-09-16  2:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15  8:22 Tricks to speed up kernel builds Ozan Çağlayan
2009-09-16  2:35 ` Thomas Fjellstrom [this message]
2009-09-16  2:49   ` david

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=200909152035.50814.tfjellstrom@shaw.ca \
    --to=tfjellstrom@shaw.ca \
    --cc=linux-kernel@vger.kernel.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