What kind of build times do you get when doing a complete clean build? And on what kind of machine?
Currently I'm only working on a notebook (three years old, and lets just say I bought it for the daylight readable screen and light weight, not its performance) and frankly this is starting to be a nuisance. Usually a complete build takes about six hours or so, but recently it took as much as ten hours... (Probably because part of the time I was also doing something on the side, but still.) As a stop gap measure I've now started using ccache, but obviously that doesn't help much when doing normal builds.
So I'm beginning to consider buying a new machine and am wondering what sort of improvement I can expect from what kind of machine (using a complete clean build as a kind of benchmark).
BTW, I'm running Windows with btool so this is without making use of both cores of my machine. If anyone has any tips for building Inkscape on Windows using two cores, I'd love to try it out and see how much of a difference that makes.
On Mon, 01 Aug 2011 12:03:40 +0200, Jasper van de Gronde wrote:
What kind of build times do you get when doing a complete clean build? And on what kind of machine?
About three years ago, a clean build on Linux took about 50 minutes on a single core AMD 3000+ desktop (that CPU model would have been about 6 years old or so by now). At that time I switched to an "AMD Phenom X4 9850 2.5GHz 4MB AM2+ Black Ed.", which dropped the compilation time to 7-8 minutes. So anything more than an hour would be ridiculously long IMHO. Unless you'd try to compile inkscape on your smartphone ;-)
BTW, I'm running Windows with btool so this is without making use of both cores of my machine. If anyone has any tips for building Inkscape on Windows using two cores, I'd love to try it out and see how much of a difference that makes.
for n cores, compilation time will be reduced approximately n-fold. At least that's my experience. So get a quad core, a SSD, and start using all cores (which is easy on Linux, and cannot be done using btool AFAIK. How about cmake?)
Regards,
Diederik
On a laptop with Intel Core i5 M460 (2.53Ghz) (2cores+hyperthreading), with 4GB RAM, Win7-64bits, a clean build is approximatively completed in 1h20min
2011/8/1 Diederik van Lierop <mail@...1689...>
At that time I switched to an "AMD Phenom X4 9850 2.5GHz 4MB AM2+ Black Ed.", which dropped the compilation time to 7-8 minutes.
@Diederik, I'm crying right now :) what's your secret ?
7-8 minutes.
@Diederik, I'm crying right now :) what's your secret ?
Just make sure that all cores are used, so don't use btool. That might be difficult on Windows, but maybe Campbell Barton's cmake efforts will bring some relieve soon? On Linux all I do is "make -j4" instead of plain "make", to use 4 cores.
Regards,
Diederik
Pentium 4 3.2 GHz, 2 Gb Ram, Windows XP: never checked exactly but let me say few hours (maybe 3 or 4, surely more than 2). I usually launch the clean build and forget it, keeping working on the machine. Then when I don't hear the fan anymore and realize that the system has regained it's normal speed, I take a look and usually it's finished.
Vista 64 bit, on a Q6600: roughly 34 minutes for a clean build (btool which uses only one core)
On Mon, 2011-08-01 at 12:03 +0200, Jasper van de Gronde wrote:
What kind of build times do you get when doing a complete clean build? And on what kind of machine?
Currently I'm only working on a notebook (three years old, and lets just say I bought it for the daylight readable screen and light weight, not its performance) and frankly this is starting to be a nuisance. Usually a complete build takes about six hours or so, but recently it took as much as ten hours... (Probably because part of the time I was also doing something on the side, but still.) As a stop gap measure I've now started using ccache, but obviously that doesn't help much when doing normal builds.
I went from a 6.5 year old notebook... build times about an hour... to a 4 core (8 threads) Sandy Bridge laptop with Sata III SSD. It takes about 6.5 minutes to do a complete build. Life is good.
Tav
I have essentially the same setup and experience as Diederick. <10 mins on a Phenom X4, 3 GB RAM in linux using make -j4.
AV
On 1 August 2011 12:55, Tavmjong Bah <tavmjong@...8...> wrote:
On Mon, 2011-08-01 at 12:03 +0200, Jasper van de Gronde wrote:
What kind of build times do you get when doing a complete clean build? And on what kind of machine?
Currently I'm only working on a notebook (three years old, and lets just say I bought it for the daylight readable screen and light weight, not its performance) and frankly this is starting to be a nuisance. Usually a complete build takes about six hours or so, but recently it took as much as ten hours... (Probably because part of the time I was also doing something on the side, but still.) As a stop gap measure I've now started using ccache, but obviously that doesn't help much when doing normal builds.
I went from a 6.5 year old notebook... build times about an hour... to a 4 core (8 threads) Sandy Bridge laptop with Sata III SSD. It takes about 6.5 minutes to do a complete build. Life is good.
Tav
Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 01-08-11 13:55, Tavmjong Bah wrote:
On Mon, 2011-08-01 at 12:03 +0200, Jasper van de Gronde wrote:
What kind of build times do you get when doing a complete clean build? And on what kind of machine?
Currently I'm only working on a notebook (three years old, and lets just say I bought it for the daylight readable screen and light weight, not its performance) and frankly this is starting to be a nuisance. Usually a complete build takes about six hours or so, but recently it took as much as ten hours... (Probably because part of the time I was also doing something on the side, but still.) As a stop gap measure I've now started using ccache, but obviously that doesn't help much when doing normal builds.
I went from a 6.5 year old notebook... build times about an hour... to a 4 core (8 threads) Sandy Bridge laptop with Sata III SSD. It takes about 6.5 minutes to do a complete build. Life is good.
Thanks for all the replies, it looks like there are some definite gains to be had :) Not the least of which is to parallelize the build process. I think I'll go shopping. (BTW, Tav, what sandy bridge processor do you have?)
Am Montag, 1. August 2011, 14:44:01 schrieb Jasper van de Gronde:
On 01-08-11 13:55, Tavmjong Bah wrote:
I went from a 6.5 year old notebook... build times about an hour... to a 4 core (8 threads) Sandy Bridge laptop with Sata III SSD. It takes about 6.5 minutes to do a complete build. Life is good.
Thanks for all the replies, it looks like there are some definite gains to be had :) Not the least of which is to parallelize the build process. I think I'll go shopping. (BTW, Tav, what sandy bridge processor do you have?)
Make sure not to underestimate the influence of operation system & filesystem. (IIRC, NTFS is quite slow.)
Best, Hans (happy Linux user)
On Mon, Aug 1, 2011 at 10:53 PM, Hans Meine <hans_meine@...240...> wrote:
Am Montag, 1. August 2011, 14:44:01 schrieb Jasper van de Gronde:
On 01-08-11 13:55, Tavmjong Bah wrote:
I went from a 6.5 year old notebook... build times about an hour... to a 4 core (8 threads) Sandy Bridge laptop with Sata III SSD. It takes about 6.5 minutes to do a complete build. Life is good.
Thanks for all the replies, it looks like there are some definite gains to be had :) Not the least of which is to parallelize the build process. I think I'll go shopping. (BTW, Tav, what sandy bridge processor do you have?)
Make sure not to underestimate the influence of operation system & filesystem. (IIRC, NTFS is quite slow.)
Best, Hans (happy Linux user)
automake defaults to include debug flags which made a noticeable difference when comparing with cmake early on so you could try remove -g flag if you are not debugging.
default cmake, using "make -j6" on my AMD Phenom II X6 1055T linux system does a full build in 4min, 17sec.
On Mon, 2011-08-01 at 14:44 +0200, Jasper van de Gronde wrote:
On 01-08-11 13:55, Tavmjong Bah wrote:
On Mon, 2011-08-01 at 12:03 +0200, Jasper van de Gronde wrote:
What kind of build times do you get when doing a complete clean build? And on what kind of machine?
Currently I'm only working on a notebook (three years old, and lets just say I bought it for the daylight readable screen and light weight, not its performance) and frankly this is starting to be a nuisance. Usually a complete build takes about six hours or so, but recently it took as much as ten hours... (Probably because part of the time I was also doing something on the side, but still.) As a stop gap measure I've now started using ccache, but obviously that doesn't help much when doing normal builds.
I went from a 6.5 year old notebook... build times about an hour... to a 4 core (8 threads) Sandy Bridge laptop with Sata III SSD. It takes about 6.5 minutes to do a complete build. Life is good.
Thanks for all the replies, it looks like there are some definite gains to be had :) Not the least of which is to parallelize the build process. I think I'll go shopping. (BTW, Tav, what sandy bridge processor do you have?)
i7-2720QM
I am also using Linux.
2011/8/1 Jasper van de Gronde <th.v.d.gronde@...528...>:
Currently I'm only working on a notebook (three years old, and lets just say I bought it for the daylight readable screen and light weight, not its performance) and frankly this is starting to be a nuisance. Usually a complete build takes about six hours or so, but recently it took as much as ten hours... (Probably because part of the time I was also doing something on the side, but still.) As a stop gap measure I've now started using ccache, but obviously that doesn't help much when doing normal builds.
Ten hours is ridiculously long even when using btool. I get far lower times (1.5h max) in virtualized Windows XP. I think the build process might be RAM starved. You need at least 1.2GB of free RAM to keep all files in the page cache.
So I'm beginning to consider buying a new machine and am wondering what sort of improvement I can expect from what kind of machine (using a complete clean build as a kind of benchmark).
Go for a multicore machine with at least 4GB of RAM. I have Intel Core i7-920, from the low end of the i7 family, 6GB RAM and a standard HDD, and a clean build with make -j8 takes only a few minutes. Most of the time on small rebuilds (e.g. a few files changed) is actually spent processing the Autotools cruft in makefiles, and linking is a close second.
Regards, Krzysztof
On 01-08-11 18:47, Krzysztof Kosiński wrote:
2011/8/1 Jasper van de Gronde <th.v.d.gronde@...528...>:
Currently I'm only working on a notebook (three years old, and lets just say I bought it for the daylight readable screen and light weight, not its performance) and frankly this is starting to be a nuisance. Usually a complete build takes about six hours or so, but recently it took as much as ten hours... (Probably because part of the time I was also doing something on the side, but still.) As a stop gap measure I've now started using ccache, but obviously that doesn't help much when doing normal builds.
Ten hours is ridiculously long even when using btool. I get far lower times (1.5h max) in virtualized Windows XP. I think the build process might be RAM starved. You need at least 1.2GB of free RAM to keep all files in the page cache.
1.2GB!!! In any case, since my machine has 2GB, that's indeed not an unlikely contributor to lengthy build times.
(BTW, the ten hours was exceptional even for me, half that is more typical.)
So I'm beginning to consider buying a new machine and am wondering what sort of improvement I can expect from what kind of machine (using a complete clean build as a kind of benchmark).
Go for a multicore machine with at least 4GB of RAM. I have Intel Core i7-920, from the low end of the i7 family, 6GB RAM and a standard HDD, and a clean build with make -j8 takes only a few minutes. Most of the time on small rebuilds (e.g. a few files changed) is actually spent processing the Autotools cruft in makefiles, and linking is a close second.
I'm now trying to find a quad core laptop (a desktop machine isn't really an option for me at the moment) that isn't too heavy, apparently a tricky combination, so I'll probably have to compromise somewhere.
On Tue, Aug 2, 2011 at 8:10 AM, Jasper van de Gronde <th.v.d.gronde@...528...> wrote:
On 01-08-11 18:47, Krzysztof Kosiński wrote:
2011/8/1 Jasper van de Gronde <th.v.d.gronde@...528...>: Go for a multicore machine with at least 4GB of RAM. I have Intel Core i7-920, from the low end of the i7 family, 6GB RAM and a standard HDD, and a clean build with make -j8 takes only a few minutes. Most of the time on small rebuilds (e.g. a few files changed) is actually spent processing the Autotools cruft in makefiles, and linking is a close second.
I'm now trying to find a quad core laptop (a desktop machine isn't really an option for me at the moment) that isn't too heavy, apparently a tricky combination, so I'll probably have to compromise somewhere.
Again, if compiling in Windows, at least for the time being if using btool, it's going to be a wait. I would consider dual booting if you're wanting to make changes and check right away to see if all works as expected. If you can splurge for an i7, you really should go for it (to get 8 threads going at once). Also, if you can get a smoking deal on a laptop that supports ddr3, if it doesn't come with a ton of ram, you can get it for dirt cheap these days (I've seen 8gigs of ddr3 laptop ram go for $55 recently).
Cheers, Josh
2011/8/1 Krzysztof Kosiński <tweenk.pl@...400...>:
Go for a multicore machine with at least 4GB of RAM. I have Intel Core i7-920, from the low end of the i7 family, 6GB RAM and a standard HDD, and a clean build with make -j8 takes only a few minutes. Most of the time on small rebuilds (e.g. a few files changed) is actually spent processing the Autotools cruft in makefiles, and linking is a close second.
I remember discussing the jobs thing with Kees a few years back and he mentioned that you should actually assign jobs for all devices (not just cores/threads) to maximize speed. Basically -j9 if you have one HDD in the mix as well, -j10 if you have a RAID with two drives, etc. I don't recall all the details about it, but it does make a slight difference in my experience.
Cheers, Josh
participants (11)
-
Alex Valavanis -
Campbell Barton -
Diederik van Lierop -
Hans Meine -
Jasper van de Gronde -
Josh Andler -
Kris De Gussem -
Krzysztof Kosiński -
LucaDC -
Tavmjong Bah -
Yann Papouin