Jeff Baxter

You know, I guess the best example is, you know, if you go to the Cheesecake Factory, this may not go for all of our global audiences, right?

And they hand you the menu, and it's 53 pages in 8-point font.

You know, you're happy to know the kitchen can make all that, but you kind of want to look at the daily specials menu, right?

You know you can go order off the 85-page menu if you need to, and you know you have APIs behind.

You know you can orchestrate all that.

But really, we need to make things a lot simpler so that you can say, you know, I just kind of want some meat today.

Or, you know, I just kind of want some pasta today.

I kind of want my pasta to look like this, you know?

Totally.

That's what we're going for.

Yeah, so we introduced 9.2.

So we introduced when, you would know, QoS minimums was what, 9.0 or 8.3?

I'm trying to remember.

Yeah, so we've introduced QoS maximums in ONTAP now for a year or more.

Um, to really help in a lot of ways, restrict performance of individual apps.

And so you could kind of balance out your system if you wanted to go apply QS maximums to everything and apply policy groups to everything.

And it was good if.

Um, you know, especially if you're a service provider or active, like a service provider, your internal customers, and you wanted to provide an individual application or set of storage objects, you know, they paid for.

30,000 IOPS, and then we're going to get 30,000 IOPS, right?

So it was pretty good for that.