News for hackers. Stuff that matters.
[deleted]
Re:GCC and C vs C++ Speed, Measured by RustyRussell on Thursday March 21, 2013 @05:04AM (#5413842)
My kernel compiles are definitely not I/O bound :) The CPU sits close to 100% for most of the compile, running cc1 as you'd expect.
Re:GCC and C vs C++ Speed, Measured by kryptiskt on Thursday March 21, 2013 @05:17AM (#5413874)
It's certainly not IO-bound. Think about the Linux kernel. It's compiling on the order of 100MB of source code into something of the same order of magnitude of binary objects, and it takes minutes. That is a not close to saturating any kind of disk device. Not to mention that the intermediate files will be cached in RAM by the file cache and can be used without them hitting the disk.
Re:GCC and C vs C++ Speed, Measured by Tobu on Thursday March 21, 2013 @06:07AM (#5414009)
My kernel directory is 13GB, most of that is intermediate build products. Linus has written somewhere on how much faster kernel compilation is with an SSD.
Re:GCC and C vs C++ Speed, Measured by kryptiskt on Thursday March 21, 2013 @07:59AM (#5414433)
My dual-SSD striped setup with humongous throughput (600MB/s) made a kernel compilation 1.4% faster compared to using a 5400rpm HD. But then I have 16GB RAM, and RAM is a huge bottleneck in its own right, as swapping or pushing out the file cache will kill compilation times.
Re:GCC and C vs C++ Speed, Measured by cperciva on Thursday March 21, 2013 @05:00AM (#5413833)
Unless you're building OpenOffice, everything is cached after the first compile finishes. Compiling hasn't been I/O bound for several years.
Re:GCC and C vs C++ Speed, Measured by Tobu on Thursday March 21, 2013 @05:33AM (#5413914)
> I don't think compilation is CPU-bound - it's probably closer to 50/50 between CPU & I/O, if not outright I/O-bound. So, is compiling the kernel really a good benchmark for what you're trying to measure?

> The result is in line with what I'd expect, though :)

> [EDIT] Well, it depends: http://stackoverflow.com/questions/15199356/speed-up-compile...

On first run without an SSD it certainly would be (linking the modules of a distro kernel, particularly so). The rest depends on rusty's setup, and in 14 minutes, it looks like it was a trimmed down build that could fit in memory.