Date: Mon, 10 Feb 2014 06:45:12 +0100 From: "army.of.root" <army.of.root@gmail.com> To: Tim Daneliuk <tundra@tundraware.com>, freebsd-stable@freebsd.org Subject: Re: And Here I Thought buildworld/makeworld Was IO Bound Message-ID: <52F86768.9000109@googlemail.com> In-Reply-To: <52F84AF8.8050007@tundraware.com> References: <52F84AF8.8050007@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 10/02/14 04:43, schrieb Tim Daneliuk: > For some years now, I have been doing nightly builds of -STABLE > on an old Pentium D machine with 2G of memory. Buildworld + 2 > different kernels was taking in the neighborhood of 3 1/2 hours or so > to run. > > I then upgraded the Mobo/CPU to a Haswell Quadcore I5-4570 and, sure > enough, the build time for all the above came down to 30-35 mins or so. > > "So", says I, "I'll bet a faster drive would help considering all the > scribbling to the disk the compilers and makes do". So, I upgdared to > a Kingston SSD Now 300, 120G hard drive and he time to do the above > went down to .... wait, it's still about 30-35 mins ???? > > So, I've tried fiddling with different values for -j on the make > command line to little avail. Well, -j8 and -j16 show no real > difference here. > > So is the bounding function here actually CPU not IO? Am I missing > something? > > Thanks, > > P.S. Trying now with no -j arg on make invocation. Hi, the new machine has a lot more memory, I assume. The build probably will not even hit the disk due to caching. Also remember, the build process spawns probably millions of processes and that alone takes some time. And 30min sounds pretty great to me :D Best regards
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52F86768.9000109>