SCSI Vs. IDE: The Showdown

Home

Basics

Configuration

Standards

Termination

SCSI vs. IDE

Hardware

Setups

Jargon

Credits

Links

Coming Soon

Last Updated:

I hate the dredge up this old flame-filled debate, but here goes.

IDE SCSI
Pros
  • Inexpensive
  • Universally accepted (virtually)
  • You already have the adapter and cabling
  • Pretty easy to set up
  • Once again, it's cheap
  • With the advent of Ultra ATA, it' really not that slow anymore
  • Low CPU usage
  • Easily supports many devices
  • Flexible configurations
  • True multi-tasking system
  • Distance between host and device can be very great (as in kilometers)
  • Easily expanded in the future
Cons
  • Somewhat slow
  • Limited flexibility
  • Limited number of devices
  • Not a multi-tasking system (see below for more explanation)
  • Higher CPU usage (Has come down with DMA, though)
  • It's expensive
  • Can be difficult to setup
  • Problems can be hard to pinpoint

What I mean by multi-tasking is this: on an IDE cable there never can be more than one process occurring.  All tasks sent down the cable must wait for the previous task to completely finish.  If a task is going to take a long time, tough luck.  On a SCSI bus more than one task can exist, and they can execute out of order.  For example, if task A is sent to a slow CD-ROM to get a chunk of data, and immediately afterword task B is sent to a speedy Seagate Cheetah hard drive, the SCSI controller can put a hold on task A and let task B go through.  This lets the main CPU spend less time waiting for things to get done and more time processing information.  I need to give a bunch of credit to Gary Field's SCSI FAQ for this last paragraph.

I was looking through Adaptec's site and I came across an article comparing SCSI and Ultra DMA.  I didn't read it over that carefully but I assume it's not totally biased.  Here's the link.