Pro-289 Posted December 16, 2013 Share Posted December 16, 2013 I'm sure other people have done speed tests and know already that parity drives slow down writes to the array. But I was just experimenting with a speed test with and without a parity drive. I have a gigabit network and transferred over a 4.36GB file. With the parity drive it took 113 seconds. Without the parity drive it took 48 seconds. Pretty big difference, cuts the time down more than half. My peak bandwidth was almost 900 Mbps. In the picture below you can see a visual on the actual test using DUMeter. Just thought it was interesting and figured I'd share it with everyone. Quote Link to comment
c3 Posted December 17, 2013 Share Posted December 17, 2013 Yes, parity slows down the write performance, but not as slow as data loss... That is the point of unRAID. Have you tuned your system? http://lime-technology.com/forum/index.php?topic=29009.0 Quote Link to comment
jbartlett Posted December 17, 2013 Share Posted December 17, 2013 There's also a feature being considered being re-added back to UNRAID that would allow parity writes to be vastly faster if all drives are spun up. It was taken out in the past as it proved to be a hindrance for larger arrays back in the IDE era. Quote Link to comment
dirtysanchez Posted December 17, 2013 Share Posted December 17, 2013 There's also a feature being considered being re-added back to UNRAID that would allow parity writes to be vastly faster if all drives are spun up. It was taken out in the past as it proved to be a hindrance for larger arrays back in the IDE era. The ability to use reconstruct-write mode was added in 5.0.3. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.