Tim, Michael,
Thanks for the replies, I will try and explain the grey parts again.
There are too many variables here. Copied what? From what to what?
I did a very simple test. I copied the same amount of data (2.72 GB) from a
partition of the SATA disk to another partition. Keeping everythiung
constant during the series of tests. I defragmented the drives before
starting.
How do you know the performance is “equiv”? Just your gut feel? Or do
you actually have some megabytes-per-second numbers?
Well, I did clock the time taken. Ofcourse I didn’t have h2bench of Iometer
to help me, it was just for a basic home based test, so a stop watch was all
I had. I could ofcourse find out the numbers by doing the calculations.
Serial ATA is not an automatic performance windfall. Is it possible
your old system had a “hot” hard disk? A great IDE disk with a good
cache will perform just about the same as an average Serial ATA disk
No it didn’t. It was one of samsungs low end drives that ship in India which
you can acquire for a few dollars. 7200 RPM if I am not mistaken, and more
over the older machine was a celeron ( I also tried a P-III), celeron having
a max FSB speed of 100 Mhz. Thus this point is ruled out.
Copying is not a good measure of system performance. Your bottleneck is
the disk, so you get no benefit at all from your faster processor.
Yes I know, but I have seen P-IVs working a ziupping fast speeds before
WITHOUT any sort of tweaking at all. I am surprised that the same copy of
the Windows XP CD ( I have licences, please don’t start away in that
direction )is not getting me the same results.
It isn’t that easy. When you access a disk, you aren’t using just one
“driver”. Instead, your requests are passing through a driver “stack”.
>The disk driver is in the middle of that stack, with (possibly) a bus
driver below, and file system drivers and filters above. The rest of
the stack is part of the operating system.
Tim, I am into storage driver development myself, though a newbie still, I
have developed 2 disk filter drivers, so I guess I you can be a little more
technical with me. What I don’t know here, is what all OS drivers the Intel
installer package replaces. The CD, has three sections, video, audio (these
two are not of any concern) an the third are th chipset drivers. I don’t
know if they replace the entire stack, or add a special driver for the SATA
controller and I/O chipsets.
My laymans understanding goes like this…if I install the drivers that come
with a particular device, I stand better chances of getting better service,
as they are custom written.
Note that you are still working from hearsay here. The only way you
could know whether the operating system is part of the problem is to do
the upgrade and redo your benchmarks.
I did, I started off with windows 2K pro basic installation without intel
915 drivers. Did the copy operation noted the time. Now I installed the
drives, and did the test again. Not much improvements.
Then I installed Windows 2K3, without drivers did the test there was a
significant difference in time around 30 seconds gain on the same data, same
copy operation. then I installed the drivers on this OS, and ran the test,
this time there was a gain of 35 seconds on the 2K times.
So can I conclude that the OS caching algos play a role here. Oh yes, I more
thing, the CD just had one installer MSI, I don’t know whether it had
custom drivers for each versoin of the OS or not.
Who’s ATA HBA drivers are you using?
Michael, I guess I am using the Microsoft supplied ones, unless your
installer does away with it. I have to do a recheck on this one.
The dog-slow performance sounds a
lot like PIO-configured MS drivers are in action here.
NO IT IS NOT. Yes, I am using caps, as I AM ABSOLUTELY sure on this. I
myself configured it to use DMA.
Unless my memory
is broken (again!) when the Win2k in-the-box ATA driver is running then
the disk is possibly running in PIO mode, and for SATA even though data
is always transferring by DMA the overhead for the whole process will
bring your machine to it’s knees.
Correct.
Verify this by looking at the disk
controller settings in the device manager and make sure the channels are
operating DMA and not PIO. Good luck, MKE.
Yeah I did, and I did change it to use DMA and reboot, before all tests.
Any pointers???
amitrajit