On Tuesday, 10 April 2018 22:53:36 UTC+1, Vir Campestris wrote:
On 10/04/2018 14:09, whisky-dave wrote:
Years ago, well the early 2000s I heard that some buses would only run at the speed of the slowest device, so if you had a CD/DVD drive in the same chain (IDE) then you're HDs would run at the same speed as the CD drive so not very fast.

That's not why an SSD is faster.

I never said it was the reason and I didn;t say anyhting about teh speed of SSDs.



With a conventional spinning rust disk to read something off the disk
you have to
1 Send it a command
2 Have it work out what you mean
3 Move the heads across the disk to the right track (like selecting a
track on an LP)
4 Wait for the disk to go around to the right position
5 read the data off the disk
6 transfer the disk to the PC.

The old PATA CD slowdown thing affected #6 only.

No what happened I think it was APTI ver. 4 where the max bus speed of 66MHz went down to 33MHz if a CD drive was on the same bus.


On a spinning rust disc 3 & 4 will both take several milliseconds, and
are the slowest part of the whole process.

Irrelevant and I think those that use the term spinning rust might not know what they are talking about.


On an SSD steps 3 & 4 are missing from the sequence.

So.


SSDs _do_ have one problem spinning rust discs don't, but you rarely see
it - if you write a _LOT_ of data they can run out of spare blank space
to write to, and they have to slow down while they clean a bit more.

They don;t have to slow down, what happens with SSDs is that the data can't be overwritten (currently), so what you need to do is actually erase the data rather than just the link to that file like you did with HDs.

The
trim command (hi John!) is designed to let it know about free space it
can erase in advance.

Not really a problem nowerdays


Andy