3 ms·
> I'm asking this from dev-centric PoV If you are doing any sort of database work with a fair number of writes and/or a dataset larger than fits neatly in RAM,
by dspillett 12y ago
> I'm asking this from dev-centric PoV
If you are doing any sort of database work with a fair number of writes and/or a dataset larger than fits neatly in RAM, it can make a lot of difference.
Other than that I don't tend to notice much change until I'm trying to do two or more things at once (opening and using other apps while a large build or test set is running for instance), at which point the difference can become pretty significant. With spinning metal other interactive work while that sort of thing is happening in the background is painful, with the SSD there is still some I/O contention but the near-zero latency (due to no head movements) greatly reduces the overall effect. The lower latency often means builds/tests stop being I/O bound (waiting for head movements) much at all and the CPU becomes a more significant bottleneck (particularly for tasks that don't/can't parallelise so are stuck on a single core) further reducing the I/O contention with interactive use (or allowing you to run several of those now-core-bound processes concurrently instead of sequentially).