VMstore performance

View trends

IOPS

15,736 IOPS

1,269 - 19,073

 

Throughput

321 MBps

57 - 659

 

Latency

1.0 ms

7.5 ms

Flash hit ratio

100 %


Performance Reserves

49% free

auto allocated
free
51% used

Physical Space

9.7 TiB free

other
live data
snapshots
free
284.2 GB used (10%)
3.6 TIB Logical (10.2x space savings)

Protection

0 MB replicated a day

Performance reserves changers

New_DB 26.4% 26.4
MySQL VM0.6% -9.4
Test_411.2%   9.3
RHEV_VM0.8%  -5.9
OpenStack VM16.1%  -4.5
HyperV VM30.6%  -3.9
HyperV VM40.2%  -2.8
XenServer VM11.5% 1.5
Eng Desktop_NewHire6.3% -0.9
Sales Desktop_NewHire0.6%  0.6

Space Changers

HyperV VM30.2 GB 0.2
SWDev_2 57.5 GB 5.0
Test_40.2 GB 0.2
RHEV_VM0.2 GB 0.2
XenServer VM10.2 GB 0.2
MySQL VM0.2 GB 0.2
OpenStack VM10.2 GB  0.2
HyperV VM457.5 GB 5.0
Eng Desktop_NewHire0.2 GB 0.6
Stats at 01:54 pm | Refresh
Service Groups
VM IOPS MBps Latency ms Provisioned GiB Used GiB Change MB/day High frequency snapshots
New_DB
7,807
84.6
1.4
53
24.9
1,555 disabled
MySQL VM
4,512
78.1
0.8
36
0.0
2,110 disabled
Test_4
4,127
64.3
0.7
42
1,265 disabled
RHEV_VM
3,180
52.2
0.7
32
0.3
1,894 disabled
OpenStack VM1
1,755
50.8
0.5
78
0.4
925 disabled
HyperV VM3
1,432
32.4
0.3
24
900 disabled
HyperV VM4
1,288
31.6
0.3
40
1,328 disabled
XenServer VM1
0
0.0
0.0
50
0 disabled
Eng Desktop_NewHire
4
0.1
1.3
108
0 disabled
Sales Desktop_NewHire
0
0.0
0.0
51
0 disabled
1 to 28 | 77 Total    | Show graphs
Sat 3:00PM Wed 2:50AM Sat 2:50PM
Virtual Disk content
Snapshots


You’ve arrived at your Tintri dashboard to solve a problem. Your VM “New_DB” has gone rogue. It’s using up too many IOPS and risks starving other more critical VMs.

Mission: Set a MAX Quality of Service (QoS) ceiling to get this VM back under control.

Action: Find the rogue VM at the top of your “Performance changers” list. Click on it.

Here is more detail on the VM in question. Scroll down to the graph below and it’s clear it has started to misbehave. Time to tame it.

Action: Right click on the New_DB VM in the table at the top of the screen.

Action: Good. Now select “Configure QoS”.

Action: We’re here to set a ceiling, so select the “Maximum” option.

In the past this VM has operated at around 2000 IOPS, so enter that MAX into the text box that just popped up .

That rogue VM was no match for you. If you need to adjust the MAX IOPS further, you can just drag and drop the line on the graph.

Summary: You set QoS for IOPS to contain a rogue VM.

RETURN TO TINTRI HUB