Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Where is the speed bottleneck in unraid? what to replace to speed things up?

Featured Replies

Where's the bottleneck when using unraid? is it disk speed? motherboard bandwidth? controller bandwidth? processor?

 

Would I get better write performance if I switch to some pci express SATAII controllers and fast drives? or would I benefit more from a faster processor? (running a 3.2ghz p4 w/ hyperthreading 2gb of ram)

Drive speed and bus bandwidth (controller) are the top factors.

 

Most motherboard built-in controllers have optimal bandwidth so converting from them to PCI Express wont be worth it. However, switching from PCI to PCI Express could be worth it, depending on the number of drives connected to the controller. IIRC, PCI has a limitation of 133 MB/s and a PCI Express single lane (1x) is 250 MB/s.

  • Author

When writing to the array, the rotational speed of the disks involved (both parity and the data disk) will usually be the limiting factor.  Each block written must first be read from the drives involved and then THE PLATTER MUST SPIN AROUND, AT LEAST ONCE, TO GET THE DISK HEAD BACK TO THE SAME SECTOR TO WRITE IT.

 

 

Something about this doesn’t make sense. How can it read something from the disk before it is written?

 

When I copy some data to the server, does it write to the disk, then re-read that data from the disk in the unraid server, calculate the parity, and then write to the parity disk?

 

When writing to the array, the rotational speed of the disks involved (both parity and the data disk) will usually be the limiting factor.  Each block written must first be read from the drives involved and then THE PLATTER MUST SPIN AROUND, AT LEAST ONCE, TO GET THE DISK HEAD BACK TO THE SAME SECTOR TO WRITE IT.

 

 

Something about this doesn’t make sense. How can it read something from the disk before it is written?

 

When I copy some data to the server, does it write to the disk, then re-read that data from the disk in the unraid server, calculate the parity, and then write to the parity disk?

 

 

No, it does not re-read the data just written, but it must first read the existing contents of both the data block being over-written, and the existing contents of the parity block to be written, before it can write to either.

 

This post may help (need to think of it at the individual bit level) : http://lime-technology.com/forum/index.php?topic=4390.msg40666#msg40666

 

Joe L.

  • Author

Now I see why the writing process is so slow :)

 

thanks for the links, very informative.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.