I'm hoping someone can clear this up for me, because I don't have the resources to test for myself. I'd like empirical data, but theory will also be welcome.
If you put 2 IDE drives on the same channel, what (if any) performance implications are there?
I've heard the following:
1) Both drives will function at the speed of the slowest drive, even if only one is in use. I find this unbelievable - I've had a HDD and a CDROM sharing the same channel and I was getting more than 7MB/s off the HDD.
2) Both drives will be limited to the ATA standard of the lowest. For example, an ATA-100 compliant HDD on the same channel as an ATA-33 compliant optical drive will function as an ATA-33 HDD, with a limit of 33MB/s shared between both drives. I see how this could be possible, but I don't think it's true.
3) The only effect is on access time, as only one request for access can be processed at a time. If a request for access for one drive comes in while a request for access to the other drive is being processed, the second request will have to wait until the first has been processed. This is an issue if a HDD and an optical drive are on the same channel, due to the relatively long access time of optical drives. I know this used to be the case, but I thought it no longer applied.
4) Using two drives on the same channel simultaneously is extremely inefficient. Some people have said this is because it's actually impossible and what is happening is time-slicing between the two drives. Others say that there are some vaguely specified overheads in using two drives on one channel that drastically reduce performance.
5) It has no effect at all, unless the combined transfer rates of the drives exceeds the practical limit of the motherboard (e.g. probably about 80MB/s for ATA-100).
I'm not sure which of those is true. I can see an effective way to test it - take 2 HDD and set them up as a striping RAID on separate channels, then benchmark. Put them on the same channel and benchmark again. Ditto with some copying, to see the possible effect of reading one drive and writing to another at the same time. Unfortunately, I don't have the hardware to do that.
If you put 2 IDE drives on the same channel, what (if any) performance implications are there?
I've heard the following:
1) Both drives will function at the speed of the slowest drive, even if only one is in use. I find this unbelievable - I've had a HDD and a CDROM sharing the same channel and I was getting more than 7MB/s off the HDD.
2) Both drives will be limited to the ATA standard of the lowest. For example, an ATA-100 compliant HDD on the same channel as an ATA-33 compliant optical drive will function as an ATA-33 HDD, with a limit of 33MB/s shared between both drives. I see how this could be possible, but I don't think it's true.
3) The only effect is on access time, as only one request for access can be processed at a time. If a request for access for one drive comes in while a request for access to the other drive is being processed, the second request will have to wait until the first has been processed. This is an issue if a HDD and an optical drive are on the same channel, due to the relatively long access time of optical drives. I know this used to be the case, but I thought it no longer applied.
4) Using two drives on the same channel simultaneously is extremely inefficient. Some people have said this is because it's actually impossible and what is happening is time-slicing between the two drives. Others say that there are some vaguely specified overheads in using two drives on one channel that drastically reduce performance.
5) It has no effect at all, unless the combined transfer rates of the drives exceeds the practical limit of the motherboard (e.g. probably about 80MB/s for ATA-100).
I'm not sure which of those is true. I can see an effective way to test it - take 2 HDD and set them up as a striping RAID on separate channels, then benchmark. Put them on the same channel and benchmark again. Ditto with some copying, to see the possible effect of reading one drive and writing to another at the same time. Unfortunately, I don't have the hardware to do that.