How many IOPS can FAS8080 handle

[netappmagic]

FAS8080
20 CPU's

128GB

has flash pool configured.

All SAS disks

For this configuration, in general, how many IOPS can this filer handle or maximum IOPS before we see the perofrmance degraded?

Thanks for your input!

[JGPSHNTAP]

How many drives and what is the raid configuration, you need to understand that.

How big is your flash pool?

Size and configuration.

There are tons of factors

[netappmagic]

 @JGPSHNTAP

How many drives and what is the raid configuration, you need to understand that.

164 x 1TB SAS raid6-dp, 1 large aggregate.

How big is your flash pool?

11x380G SSD

Please let me know. Thanks,

[AlexDawson]

Very much dependant on workload, configuration, etc. In general, we size to workloads, not provide raw max figures, because they don't exist as such - for example, we might be able to do X00,000 IOPS at 1ms latency - but X10,000 at 2ms .. or X80,000 at 10ms - which is the right figure? 

We have a published SPC1 benchmark of an All-Flash FAS8080 at 685,000 IOPS - http://www.storageperformance.org/benchmark_results_files/SPC-1/NetApp/A00154_NetApp_FAS8080-EX_AFF/a00154_NetApp_FAS8080-EX_AFF_SPC-1_executive-summa...

Since then we have added OS optimizations etc, so this should not be considered a maximum figure - just a figure for that config.

[netappmagic]

AlexDawson,

for the same question, and same configurations as said, what if the required latency is 8 ms or below, how many IOPS can I achieve? if you can advice.

I found how  many iops that FAS8080EX (all flrash) can provide in your link, but what I am looking  for is not all flash, but FAS8080(2-node HA SAS) only, let's say there are about  72 SAS disks. 

[GidonMarcus]

Guys.

this is not straight forward. sit with your SE on their sizing tools and do the calculation with them.

in https://www.netapp.com/us/media/tr-3838.pdf  page 21 is saying a 15K SAS disk can do 176 IOPS on the back-end.

we don't know how you building your system with these 72 disks (spares?, raid type? ,raid groups count?, root aggregate?)... 

the calculation you'll get from that is your bottleneck on the back-end. but the front end activity can look completely different with caching, dedup. compression, in-memory activity (especially for NAS use),background activities...

Gidi

[AlexDawson]

As Gideon says - it is not a straight forward answer, nor a straight forward question - there are literally more than 50 different variables that goes into sizing, including read/write sizes, random vs sequential read vs write, concurrency of workloads, access protocols, version of ONTAP, etc. Depending on this data, it could be 400MB/sec to 950MB/sec, with 11,000 to 130,000 IOPS or more.

If you are concerned that your existing system is running slow, please open a support case and we will investigate.

If you are looking for a sizing for a workload as part of a potential purchase, you need to work with a solutions engineer from NetApp directly as part of the sales process.