0

Initial Configuration:

RAID:

  • Disk Drives: 6 HDD TOSHIBA MBF2600RC (600 Gb, 16 Mb, 10025 RPM, SAS, 600 Mb/s)

  • 2 Spans

  • Motherboard: SuperMicro X8DTU-6F+/6TF

  • RAID Controller: SuperMicro SMC2108

  • Virtual Group: RAID50

  • Polices:

    • Access: RW
    • Read: Normal
    • Disk Cache: Enable
    • I/O: Cached
    • Disable BGI: NO
    • Default Write: Write Through

Used Operation System: Windows Server 2016

Result:

CrystalDiskMark Metrics:

Read [MB/s]: 221.5 Write [MB/s]: 38.30 

Ubuntu Live CD Metrics:

Read [MB/s]: 270.1 Write [MB/s]: 49.5 

Question:

What can I attempt to increase Write Speed?

Should I reconfigure RAID50 settings, or configure different type of RAID?

7
  • Is this a new array? What OS? One solution would be to not use "hardware" RAID... (which has other benefits too) Commented Dec 19, 2018 at 15:53
  • "Write Through" vs "Write Back" caching will likely affect this significantly, though make sure you have NV cache (or backup power) if you use Write Back. Commented Dec 19, 2018 at 15:55
  • So... 6 disks = 2 spans of 3 disks each? Try deleting and recreating the RAID. Use a live CD to test the I/O. You could always try a different RAID type to test. Doing three mirror sets and then I/O test against each might indicate if a drive is the culprit. You could also look to the RAID controller. Make sure you're on the most updated firmware for it from the vendor. Commented Dec 19, 2018 at 15:55
  • Thanks for response. I've updated my question to clarify your notes Commented Dec 19, 2018 at 16:06
  • 1
    Write Back will give you a higher write speed... until your cache fills up... but before enabling it you must make sure that you have NVRAM or suitable backup power (e.g: battery / super cap). Commented Dec 19, 2018 at 16:16

1 Answer 1

0

Changing Default Write policy to 'WRITE ALWAYS BACK' has aligned rate of speed:

Read [MB/s]: 222.6

Write [MB/s]: 208.8

So it's a good practice to consider this option for write intensive tasks.

1
  • 3
    Write-back cache substantially increases the risk of data loss in some use cases, as it does not guarantee that the data is written to permanent media (only to the cache) -- failure without a battery-backed cache is potentially damaging. Commented Dec 19, 2018 at 18:23

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.