Sharethevibe
Dabbler
- Joined
- Aug 21, 2019
- Messages
- 21
I am building a NAS using 8x 8TB disks and am getting different info on the IOPS that I can calculate with to estimate the speed of the system. Info varies between disks-IOPS being 75 or being 600… I’m puzzled... but probably other forum users can clear this up?
Disks:
1/(avg seektime in msec+ avg latency in msec). This would give 1/(0,008+0,006) being approx 70 IOPS.
Yet, when retrieving the measured IOPS as given online in various tests, e.g. by Tomshardware.com it's:
- for read: 200-500 IOPS (queue-depth 1 to 32)
- for write: 500-600 IOPS
Source: https://www.tomshardware.com/reviews/wd-red-10tb-8tb-nas-hdd,5277-2.html.
(and this is for the 128MB cache version, where mine are 256MB).
Also, when I compare it with similar tests for 3TB WD-Red disks, these have IOPS of 100-150.
So, it seems to me that in the real-world situation, this 8TB WD NAS-disk is way outperforming it's earlier/smaller brothers, and the IOPS of 200-600 are valid for this disk-type?
(WD with this disk probably making good use of the high datadensity and of the large cache and of TLER (reducing error-seektime) and whatever tricks WD knows in diminishing the seek/latency-times etc.?).
And as the runs in my processes typically are mass/large (reads or writes of 200.000-500.000 files; files are 50MB or 10MB) I reckon that the IOPS-figures for the 'queue-depth of 32' are most valid for my processes?
NOTE: the HBA disk-controllercard is the IT-flashed Dell H310, so this I believe can deliver up to 600 queue-depth?
Can anybody shed some light on this?
(this IOPS performance will for a great deal determine the speed of the NAS, so the need of perhaps going to 3 VDevs, maintaining open pool-space, setting of max record-size).
Thanks in advance!
Disks:
- 8TB WD-Red, NAS-type, 5400rpm, 256MB cache (2018 model, type ‘EMAZ’, equal to ‘EFAZ’)
- 8 disks mounted: 2 striped VDevs of 4 disks in Z1 (2x (4x disks in Z1)
1/(avg seektime in msec+ avg latency in msec). This would give 1/(0,008+0,006) being approx 70 IOPS.
Yet, when retrieving the measured IOPS as given online in various tests, e.g. by Tomshardware.com it's:
- for read: 200-500 IOPS (queue-depth 1 to 32)
- for write: 500-600 IOPS
Source: https://www.tomshardware.com/reviews/wd-red-10tb-8tb-nas-hdd,5277-2.html.
(and this is for the 128MB cache version, where mine are 256MB).
Also, when I compare it with similar tests for 3TB WD-Red disks, these have IOPS of 100-150.
So, it seems to me that in the real-world situation, this 8TB WD NAS-disk is way outperforming it's earlier/smaller brothers, and the IOPS of 200-600 are valid for this disk-type?
(WD with this disk probably making good use of the high datadensity and of the large cache and of TLER (reducing error-seektime) and whatever tricks WD knows in diminishing the seek/latency-times etc.?).
And as the runs in my processes typically are mass/large (reads or writes of 200.000-500.000 files; files are 50MB or 10MB) I reckon that the IOPS-figures for the 'queue-depth of 32' are most valid for my processes?
NOTE: the HBA disk-controllercard is the IT-flashed Dell H310, so this I believe can deliver up to 600 queue-depth?
Can anybody shed some light on this?
(this IOPS performance will for a great deal determine the speed of the NAS, so the need of perhaps going to 3 VDevs, maintaining open pool-space, setting of max record-size).
Thanks in advance!