Jeff Baxter

We certainly intended a future release to follow on with that mass support and with support on hopefully platforms beyond AFS.

So nine dot two, you can go in and set a policy group and on your given

a LUN or a volume with LUNs, you can go ahead and set a, just like it says, a minimum IOPS.

So if you set something to be 30,000 IOPS, no matter really what's happening on the system, it's going to go ahead and ensure that that individual storage object gets the 30,000 IOPS that it's been promised.

And I'll pause for a second if you have questions here, but it's actually pretty cool how we've done it.

And we built it into the entire stack of ONTAP.

It's not just a glom on.

It's actually built all the way from the disk level up to the essentially protocol layer, how we do the QoS minimums.

Okay.

Absolutely.

And I'll take you as, I'll take you as far as the looking glass as I can.

And then I will wave a white flag and, and, uh,

We'll see.

Justin may even know more than me on it.

We'll explore the depths of my knowledge, and then I'll refer you to all the different TRs and different things we have out there.

But what I'll say about it is there are a couple of questions you had built in there.

The first thing we do is we have this feature that's built into ONTAP now called Headroom.

And it's a dynamically generated metric of basically how much performance capacity is available in the system.

And we base that on something that we call basically the sort of optimal point for the system.

It's basically the advertised performance capacity for the system.