Building speed on multi-cpu systems
Michael Pyne
mpyne at purinchu.net
Sun Feb 22 01:02:52 GMT 2009
On Saturday 21 February 2009, Alex Merry wrote:
> On Sunday 22 February 2009 00:18:22 Andriy Rysin wrote:
> > I have a 2-core cpu so I was trying to improve KDE compile speed and the
> > quickest solution I could come up with to put "-j 4" in the makeobj
> > script in the make command call (build speed was up ~30% and I in a
> > monitor I can see all cores are fully busy now). Though this solution
> > feels a bit hackish so I was wandering if there's a better/standard way
> > to do that? If makeobj is the right place may be we could make it more
> > generic so it tries to detect number of cores automagically (at least for
> > some most popular platforms)?
>
> Well, you could just pass -j4 to makeobj, which will pass it on to make.
> The best place to put that depends on what you use to build kde. If you
> use the bash scripts on techbase, then you can just edit the cmakekde
> function, which uses -j2 by default.
>
> Alex
Mind you probably the best option is -j 3 for a dual-core system (number of
CPUs + 1). The one extra process is going to be the one doing I/O, the others
will either be doing work on a CPU core or stuck waiting for I/O, so CPUs + 2
doesn't really help much.
Regards,
- Michael Pyne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090221/da5bf6c1/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090221/da5bf6c1/attachment.sig>
More information about the kde-core-devel
mailing list