Hi,
Can someone in the community or from NetApp professional services or NetApp AQoS development team provide some insight into the AQoS maths and its working.
For example:
- An application database play area is: 20gb volume with constant 200 IOPS requirement, how does this fit into the SLO Model which defines IOPS per TB?
- If the application read/write ratios change - from write to constant reads - How does it fit in to SLO mdel?
- Per TB is this for thick provisioned or Thin provisioned volumes?
- What if application is assigned 1TB thick but its never going to use that much space?
I was thinking, like a goold old school of thought - It depends how many spindles you have with cache or SSD for that volumes, and then it does not matter how much space you have given to the application, it will always have a contantst IOPS, and you should be able to control it by enforcing the IOPS bandwidth?
Some information with examples would be really appreciated.
Cheers!
Thanks,
-Ashwin