These ATTO scores...
What do you guys think of mine? This is on a WD 80 Gig SE (WD800JB).
I really dont know how to read these scores, and have no one to compair them with.
I really, really want to learn how to though! What are good scores (with RAID 0, vanilla IDE, etc), bad scores, and so on.
I really dont know how to read these scores, and have no one to compair them with.
I really, really want to learn how to though! What are good scores (with RAID 0, vanilla IDE, etc), bad scores, and so on.
0
Comments
http://www.short-media.com/forum/showthread.php?t=7718
For the record, my RAID array does over 100MB/s both reading & writing
That drive, benched near the rim, (its slower the farther in you go) should hit 50,000 to 55,000 maybe. Its fastest on the outside and slows the farther in you go. Or the fuller the drive gets if you follow me. So the score might be perfect depending on how full it is etc..
tex
here is a pretty good raid-0 to compare to.
Tex
Right on the money. Defragging before atto isnt critical as the test is so smal but Sandra.... Any fragmentation just kills your scores cause the test file is so huge and they use every teeny piece of open space from the rim on in.
Tex
It looks like you didn't turn off your folding client prior to the test. Folding hits the shorter end real hard. ishiii's score looks more representative of a single WD SE drive, although a bit low.
Well, it's about half full. I wonder what it is I could do to speed it up...
It's already in UDMA mode 5, and IDE busmastering (I think thats what it's called) is enabled in the BIOS.
I'm using the standard Microsoft IDE drivers, because the latest SW IDE drivers from nVidia has given me many problems with burning CDs. What IDE drivers are you using on your NF7-S Geeky?
Any good?
Thanks Tex.
If not, what am I doing wrong? I'm using an Abit IC7-MAX3 motherboard and the on-chip RAID controller. I haven't updated the BIOS for the mobo yet (don't know if this would affect anything or not).
Also, I have an 80 gig WD hard drive from my previous computer that I'd like to hook up. The raptors are on SATA1 and SATA2, while the 80 gig is IDE. When I plugged the 80 gig hard drive into the IDE slot, the RAID controller that shows up after POSTing didn't recognize it as a "non-RAID disk". Is there something I have to change in the BIOS?
Thanks,
Greg
Tex
When your benching further in on a pretty full drive its just a guess and really hard to tell if there is a problem unless its way out of whack.
Tex
I'm not experienced enough to be able to tell the distinction, but when I made the array I told the RAID BIOS to use 16k, so I'm guessing that's the stripe size. I used Windows default block size, which I seem to remember being 4k, so this would be a 16/4?
This was with folding on, fresh XP install, no defrag. I think it likes the big writes.
-drasnor
http://www.short-media.com/forum/showthread.php?t=668
Tex et al,
anything I'm missing here or should I be happy and shutup!?
Also, another interesting dilemma while tweaking my RAID 5 array of 4 WD JBs on a Highpoint RocketRAID 404, I noticed the controller has two separate entries in Powerstrip as well as Device Manager? According to all my online research this is normal, do I test the latency of both?
Edit: Even more confusing is that my Sisoft Sandra scores dropped from 70k to 55k after a Diskkeeper defrag. Does that make any sense? In real world applications, I haven't noticed a difference.
You should be faster then me and you are not...
Answer your question?
-drasnor
Flint
" Combining the first significant performance increase in over a year with whisper-quiet operation, Hitachi's Deskstar 7K250 proves that there's a lot of life left in the venerable 7200 RPM design. Western Digital's three-year run with the 7200 RPM ATA title has finally come to a close. Available across a wide range of capacities in both parallel and serial ATA interfaces, the 7K250 should top the list of all performance-oriented users seeking a new drive for their desktop rig.
Hitachi has easily managed to impress. We look forward to seeing what's next!"
Flint
:canflag: