4 ms·
According to his benchmarks, compilation of C code (Pidgin at least) doesn't seem to benefit from SSD, even the 5400RPM drive performs the same. SSD for develo
by vicaya 17y ago
According to his benchmarks, compilation of C code (Pidgin at least) doesn't seem to benefit from SSD, even the 5400RPM drive performs the same.
SSD for developers is usually waste of money from technical POV, as the working set usually fits in the fs page cache.
30" IPS panels, OTOH, would be money well spent.
- dagw 17y agoDevelopers often do more than simply compile code. For example if I could cut the start up time of the app I'm developing in half that would be really quite nice indeed, even if compile times stay the same.
- barrkel 17y agoI don't know about that, it depends on the build tree I guess. Our IDE build tree (which includes compiler, RTL and lots of other stuff) writes about 600M of intermediate files, 1G of executables / debugger symbol files / map files etc., and reads probably several G worth of source. A rebuild (clean and build) currently runs in about 13 minutes on my 10K drive, but I'm fairly sure it could be cut down with faster I/O.
- Janzert 17y agoActually Spolsky had already found that to be true for their compile times back in March. But decided the benefit was still worth it for his developers. See http://www.joelonsoftware.com/items/2009/03/27.html http://www.joelonsoftware.com/items/2009/03/27.html