And also vice versa (HDDs over SSDs)? My textbook is telling me that HDDs are generally used for sequential access/writes, while SSDs tend to be used for random access/write patterns. And then the authors go on to explain that depending on the workload, one may be more useful than the other. Can anybody provide some examples of what those workload models would be like in the real world? Thanks :)
| |||
|
feedback
|
This question covers exactly the same ground as earlier questions on this topic; its answers may be merged with another identical question. See the FAQ for guidance on how to improve it.
|
Databases work very well on SSDs, in practice I tend to put OSes and DBs on SSD, and large datastores on HDD | |||
|
feedback
|
|
My company makes an audio-playback application that reads multiple mono audio files simultaneously and mixes them (in real time) to an audio output... with an SSD we can mix many more input audio files at once, since we no longer pay a penalty for having drive heads constantly seeking from one file to another during playback. | |||
|
feedback
|
