SSD and programming
- by Simon Johnson
I'm trying to put together a business case for getting every developer in our company an Intel SSD drive.
The main codebase contains roughly 400,000 lines of code. My theory is that since the code is scattered about in maybe 1500 files, an SSD drive would be substantially faster for compiles. The logic being that many small reads really punishes the seak-time bottle-neck of a traditional hard-drive.
Am I right? Is SSD worth the money in productivity gains by reducing the edit/compile cycle time?