1,269 - 19,073
57 - 659
Here’s your Tintri dashboard. You’ve just been asked to onboard a new virtualized database. Can you do it without affecting the performance of your other VMs?
Mission: Determine remaining reserves and typical VM behaviors.
Action: What percentage of your reserves are “free”? Click on the number.
Clicking on your % “free” takes you to this view, so you can see how your reserves have been changing over the past 7 days. And on the right, you can see the individual VMs using the MOST performance.
Action: Which VMs are using the most IOPS? Click on IOPS in the menu in the top left corner.
Looks like your greediest VMs are consistently using around 3,000 IOPS. You expect the virtualized database you’re onboarding won’t use any more IOPS than these VMs.
Action: Lets go back to the dashboard and tie this all together. Click on the “Dashboard” tab in the top left menu.
Let’s put it all together. Your VMstore is currently using about 12,000 IOPS, and 49% of your performance reserves are available. Looks like you can easily handle the request to add another virtualized database.
You determined your remaining performance reserves from your dashboard, then drilled in to see the IOPS used by individual VMs.
Summary: You proved you can have total visibility of performance with no support calls, PerfStats or conventional complexity!