mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Brian D. McGrew" <brian@visionpro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Building the kernel on an SMP box?
Date: Sat, 29 Jul 2006 16:29:42 +0200	[thread overview]
Message-ID: <9a8748490607290729y49c66208n8b8ea5b9b29a3d06@mail.gmail.com> (raw)
In-Reply-To: <14CFC56C96D8554AA0B8969DB825FEA0012B3898@chicken.machinevisionproducts.com>

[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]

On 27/07/06, Brian D. McGrew <brian@visionpro.com> wrote:
> Good morning all!
>
> Currently I'm building my kernels on a Dell PE 1800 3.0GHz.  My dilemma
> is that I build and rebuild the kernel about twenty times a day and even
> though it only takes about 20 minutes, that's rapidly becoming too slow!
> Today it's the 2.6.17 kernel on FC5 that I'm building with.
>
> I see all these blurbs out there about someone being able to build a
> complete kernel in under a minute or running an SMP build across
> multiple CPUS and/or multiple machines.
>
> So, to ask the group that should know the best ... What would be a
> reasonable configuration to get my builds down under five minutes or so?

My box builds my ordinary .config (attached) in under 5min :

$ time make -j3
real    3m58.047s
user    4m54.574s
sys     1m24.202s

Here are some more numbers for you to compare to your box :

allnoconfig :

$ make clean
$ make allnoconfig
$ time make -j3
real    0m54.544s
user    1m2.113s
sys     0m20.781s


allmodconfig :

$ make clean
$ make allmodconfig
$ time make -j3
real    28m49.748s
user    35m3.212s
sys     10m43.633s


This box uses a Athlon64 X2 4400+ CPU, has 2GB RAM and a single
Ultra160 SCSI disk.
It's currently running an i386 kernel, not x86_64, so it's probably
not performing to it's full potential atm.


> And then to go to the extreme, what kind of horsepower should I be
> looking for if I want get the build times down to say a minute or so???
>
Make sure you have a fast disk and adequate amounts of RAM so you
don't end up swapping, then add more CPU's.
A dual-core box is not too expensive these days and an additional core
really speeds things up. If you have the money for it, then a box with
two dual-core CPU's is ofcourse even better.
If you have several machines, then you can use distcc
(http://distcc.samba.org/) to distribute the build across the boxes -
that's an easy way to speed things up if you have a bunch of older
computers lying around.


-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

[-- Attachment #2: .config.gz --]
[-- Type: application/x-gzip, Size: 7542 bytes --]

  parent reply	other threads:[~2006-07-29 14:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 14:06 Brian D. McGrew
2006-07-27 15:19 ` Rolf Eike Beer
2006-07-28  1:02 ` Bill Davidsen
2006-07-28 13:46 ` Andi Kleen
2006-07-29 19:33   ` Bill Davidsen
2006-07-29 19:29     ` Andi Kleen
2006-07-29 21:30       ` Bill Davidsen
2006-07-30 16:18       ` Valdis.Kletnieks
2006-07-30 17:11         ` Andi Kleen
2006-07-29 14:29 ` Jesper Juhl [this message]
2006-07-29 18:54   ` Handle X

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=9a8748490607290729y49c66208n8b8ea5b9b29a3d06@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=brian@visionpro.com \
    --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

all inboxes | Powered by JetHome®