Sign in with
Sign up | Sign in
Your question

RAID writes faster than it reads. Explain?

Last response: in Storage
Share
January 5, 2012 7:54:03 PM

Sooo... what would cause this, and is there possibly a lot of read speed being held back?

January 5, 2012 8:07:26 PM

hmmm r u sure that's raid score...
seem to be very slow and low score for RAID setting.
Double check with main board setting.
m
0
l
a b G Storage
January 5, 2012 8:08:52 PM

You really need to list what drives and raid type you are using as well to really be able to make anything from that screenshot.
m
0
l
Related resources
January 7, 2012 2:40:12 AM

Im thinking that because it splits it in half it faster to write. But when you need to read you got to find to halves. (Raid 0) Something similar happens with Raid 1
m
0
l
January 7, 2012 3:05:16 PM

But wouldn't that concept then double the read speed too? You're using twice the read heads just like you're using twice the write heads... seems odd to me :pfff: 
m
0
l
January 7, 2012 5:08:04 PM

Level 0:

Level 0 is a 'striped' disk array without fault tolerance. It provides data striping (spreading out blocks of each file across multiple disk drives) but no redundancy. This improves performance but does not deliver fault tolerance. If one drive fails then all data in the array is lost.



Level 1:

Level 1 does 'mirroring' and 'duplexing'. It provides disk mirroring. Level 1 provides twice the read transaction rate of single disks and the same write transaction rate as single disks.

Level 4:

Level 4 is 'dedicated parity drive'. It is a commonly used implementation of RAID. Level 4 provides block-level striping (like Level 0) with a parity disk. If a data disk fails, the parity data is used to create a replacement disk. A disadvantage to Level 4 is that the parity disk can create write bottlenecks.

This are the ones that would show something similar to this.
m
0
l
!