Community Related Discussions

number of discs relative to iops

Good afternoon, Colleagues! Please explain whether there will be a large increase in the performance of storage systems when using a system with 30 disks, in comparison with a system with 60 disks. The disks in the system are the same and the raw volume is not important. Thank you in advance


Re: number of discs relative to iops

In general, more disks means more parallelism, more IOPS. However, this is not applicable to 'Optimised Specialised Storage Systems'. These days most of the newer NetApp systems do 'abstracted IOPS' (Running :cDOT/ONTAP). The total IOPS that a node can provide is based on the physical characteristics of the node—for example, the number of CPUs, the CPU speed, and the amount of RAM. The total IOPS that an aggregate can provide is based on the physical properties of the disks—for example, a SATA, SAS, or SSD disk. Hence, the combination, CPU cores, RAM in your Node, and the number of volumes on that 'flash-pool, IOPS availability will differ but will be way greater than the actual RAW IOPS. It's bit complex but I guess its projected based on a generic workload based testing and it's different for different filer Model.


Regarding your specific query: More disks you have in your raid-group set, more IOPS will be available at RAW aggregate level (That doesn't mean putting all in the single-raid_group, there is always trade-off). As I mentioned, the actual front-end IOPS will depend on many different factors.


Considerations for sizing RAID groups:

View solution in original post

Re: number of discs relative to iops

Thanks for the quick reply, very detailed and very clear.
I want to clarify about concurrency. If we take the entire set of disks, regardless of the use of the raid level (6,10,50,60), what algorithm is used to write to the RAW array? Does recording happen on all discs simultaneously or does ONTAP select the fastest discs and write to the first one very much on them?

Re: number of discs relative to iops

Yes, it stripes across all disks, but "how it does" is perhaps already covered in tons of articles on the NetApp knowledge base/Community-forums as well as on the various blogs on the Net.  The key word here is 'WAFL', just explore for this info.


In short : NetApp storage systems comes "write-optimized" through the use of write cache and nonvolatile memory (NVRAM or NVMEM) along with the core component called 'WAFL'. Following articles will give you some useful idea on this topic.



Cloud Volumes ONTAP
Review Banner
All Community Forums