Comment Re:Bottleneck must be elsewhere (Score 3, Interesting) 205
If your running windows (NT or 2k), the bottle neck is the OS.
The NT microkernel was designed serialize all IDE device access in the drivers.
Therefore, if multiple processes are attempting concurrent IDE subsystem access, each data transfer request will run to completion.
It actually makes no difference if the processes are attempting access to different physical devices, because it is the NT driver layer that enforces this restriction.
This is especially bad for an OS that relies on a page/swap file residing on a shared resource.
Only viable solution for concurrent access: use only SCSI devices.
The NT microkernel was designed serialize all IDE device access in the drivers.
Therefore, if multiple processes are attempting concurrent IDE subsystem access, each data transfer request will run to completion.
It actually makes no difference if the processes are attempting access to different physical devices, because it is the NT driver layer that enforces this restriction.
This is especially bad for an OS that relies on a page/swap file residing on a shared resource.
Only viable solution for concurrent access: use only SCSI devices.
