Buildworld Benchmarks

krad kraduk at
Wed May 18 21:12:41 UTC 2011

On 18 May 2011 01:50, Devin Teske <dteske at> wrote:

> Hi List,
> What's the fastest anyone has every completed buildworld on a single
> machine?
> The reason I ask is because we just got some new hardware in and decided to
> benchmark it using buildworld.
> Just as a quick test, we decided to perform "make -j 48 buildworld". We
> finished
> in approximately 9 minutes.
> I think that we can improve upon that, but am having a bit of difficulty.
> Can anyone offer any pointers in how to achieve the fastest buildworld
> possible?
> No particular reason... we're just trying to push the boundaries of what's
> possible.
> For reference the machine we're compiling on is a dual-socket Nehalem Xeon
> (six-core per proc; HTT enabled; 24 total CPUs presented by APIC) with 48GB
> of
> RAM, an LSI MegaSAS RAID controller, and an LSI 2Gbps Fibre Channel HBA
> going to
> an 8TB NEC D-4 array.
> ASIDE: Doing the same buildworld on a 4-disk ZFS raidz yielded
> approximately
> 11-minutes. Performing the buildworld on the NEC D-4 over the 2Gbps FC HBA
> yielded approximately 12 minutes. And for some unknown reason, performing
> buildworld on tmpfs yielded 13 minutes.
> We thought going tmpfs would make things faster, but that resulted in over
> 13
> minutes (huh? you'd think a RAM disk would be smoking compared to even the
> SSDs
> that we used to achieve ~9 min; do note that we did make sure to nullfs
> mount a
> tmpfs-based directory onto /usr/obj -- though the performance of that
> nullfs
> mount might have hurt the test, not sure).
> --
> Devin
> _____________
> The information contained in this message is proprietary and/or
> confidential. If you are not the intended recipient, please: (i) delete the
> message and all copies; (ii) do not disclose, distribute or use the message
> in any manner; and (iii) notify the sender immediately. In addition, please
> be aware that any message addressed to our domain is subject to archiving
> and review by persons other than the intended recipient. Thank you.
> _____________
> _______________________________________________
> freebsd-questions at mailing list
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at"

to make it fair you would have to have a generic src.conf
and specify whether you used clang or gcc. As well as the release as well

More information about the freebsd-questions mailing list