[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: Building speed on multi-cpu systems
From: Michael Pyne <mpyne () purinchu ! net>
Date: 2009-02-22 1:02:52
Message-ID: 200902212003.03501.mpyne () purinchu ! net
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" \
content="1" /><style type="text/css">p, li { white-space: pre-wrap; \
}</style></head><body style=" font-family:'Droid Sans Mono'; font-size:10pt; \
font-weight:400; font-style:normal;">On Saturday 21 February 2009, Alex Merry \
wrote:<br> > On Sunday 22 February 2009 00:18:22 Andriy Rysin wrote:<br>
> > I have a 2-core cpu so I was trying to improve KDE compile speed and \
the<br> > > quickest solution I could come up with to put "-j 4" in the \
makeobj<br> > > script in the make command call (build speed was up ~30% and I \
in a<br> > > monitor I can see all cores are fully busy now). Though this \
solution<br> > > feels a bit hackish so I was wandering if there's a \
better/standard way<br> > > to do that? If makeobj is the right place may be we \
could make it more<br> > > generic so it tries to detect number of cores \
automagically (at least for<br> > > some most popular platforms)?<br>
><br>
> Well, you could just pass -j4 to makeobj, which will pass it on to make. <br>
> The best place to put that depends on what you use to build kde. If you<br>
> use the bash scripts on techbase, then you can just edit the cmakekde<br>
> function, which uses -j2 by default.<br>
><br>
> Alex<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>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.<br> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"><br></p>Regards,<br>
- Michael Pyne<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p></body></html>
["signature.asc" (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic