dslreports logo
    All Forums Hot Topics Gallery


how-to block ads

Search Topic:
share rss forum feed


Pacifica, CA

1 edit
reply to koitsu

Re: SSD Drives have arrived - I have Q's

Click for full size
Click for full size
I feel like an idiot after my previous comments. I have to tell you guys that I just could not get myself away from the RAID topic. I bought the disks with RAIDing in my heart and after they arrived I learned from you guys here that booting with this kind of configuration has proven to be more trouble than it is worth… in the long run.

Anyway, I just had to put these two disks together to see what happens and study the whole topic and get some experience with it.

I raided the disks together for the first time so I can say I am no longer a Raid virgin. Summary of what I learned:

1) WD Caviar Black Win7 boot time was 103 seconds (orig system)
2) SSD boot time after reinstall timed out to be 13.8 seconds
3) Raid of 2-SSD boot time was between 26-28 seconds for stripe sizes of 4,8,16,128k.
4) Makes no sense to stripe less than 16KB
5) Interesting that the raid throughput sums up to the sum of the specs of the disk in this case.
6) Windows experience index went from 5.9 to 7.9 from a single boot SSD to a Raided pair.

Above left is the throughput comparison of the SSDs raided together with separate Read and separate Write comparison of the 4 stripe sizes. This tells me the optimum stripe size (for these tests) would be 16KB. There is no advantage striping less than 16 from a througput standpoint and if you did, your CPU appears to become more and more stressed.

Above right is what the CPU looked like during the tests. Splitting hairs tells me just what I was expecting to see. The smaller the stripe size the more work your CPU has to do. (Note: My I860 has 4 physical + 4 Virtual CPUs so you see 8 boxes)

Finally, an example of 16KB stripe size for those that are interested. I am not passing this information out to brag... just giving out my notes which may have value to others.

Under Siege
Mcdonough, GA
·AT&T U-Verse
Click for full size
Video card is an old GTS 250/512
said by ejg1:

2) SSD boot time after reinstall timed out to be 13.8 seconds
3) Raid of 2-SSD boot time was between 26-28 seconds for stripe sizes of 4,8,16,128k.
6) Windows experience index went from 5.9 to 7.9 from a single boot SSD to a Raided pair.

Those are the strangest numbers I've seen, maybe koitsu See Profile can explain the reasons. On one hand, you have a screaming boot time, single SSD and a low WEI. On the other, you have a slower boot time RAID but a high WEI. Is there something in the RAID boot process that would slow you down?
Your WEI on single seems strange too. Your system (from what I can gather from posts) way exceed my 5yr old system (proc/memory/video) and yet my single SSD yields a greater WEI. Yes, I know I shouldn't rely on the WEI, but it is still a measurement/benchmark that is being used.
That's "MISTER" Kafir to you.


Pacifica, CA
After the single SSD install, I convinced myself that I re-triggered(updated) the score determination process of the WEI, but it came back the same numbers from after the immediate fresh install. I also second second guessed what I did but still am a little befuddled as you are.

However the Raid boot time being slower than the Single SSD boot time... google says there are lots of guys with this condition and I have yet to see a discussion that gives any kind of potential resolution.

Ukiah, CA
When are you starting the timer? When you see the Windows bootup screen or when the PC first turns on? If it's the latter, the extra time could be from the RAID option ROM kicking in (you should see an additional screen between POST and Windows).

Mountain View, CA
reply to ImpldConsent
There's really nothing to explain -- the numbers in WEI mean jack squat. They've always meant jack squat, and they will always mean jack squat. They're arbitrary numbers that represents absolutely nothing useful in the real world. There's no comparison model, there's no indication how the numbers are calculated, there's no break down of how each test affects the number, and there's no unit. For sake of example, compare what WEI gives you to, say, the above ATTO results. ATTO's numbers make perfect sense and represent something real and useful -- WEI is just a number.

Imagine going into a home repair store and telling the clerk "I need some piping". The clerk asks you "what type and what for?" and you respond "I don't know". The clerk asks you what length, and you reply "5". "Five what?" he asks, and you respond "just 5". That's WEI.

The only thing I've seen WEI used for is to determine if your system is eligible or not for Aero capability. That's it.

Otherwise I'd recommend asking about anything pertaining to WEI over on the Microsoft forum -- or better yet, ask Microsoft directly. They invented this nonsense. I'm not a Windows administrator; I do UNIX and networks.
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.

Caveat Emptor
Earth Orbit
My take on WEI...

The gamification of PC Hardware. Spend $500 on upgrading a component and see that "HIGH SCORE" number go from a 5.4 to 7.9 in psycho-emotional payoff! Elated yet? Let the serotonin flow! Aren't you addicted already???
Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety.


Lynnwood, WA
WTF is WEI? (that's my take on it)

Windows Experience Index