Unsolved

This post is more than 5 years old

3 Posts

3084

May 2nd, 2013 13:00

VNX Monitoring and Reporting - Performance Report re IOPs @ latency

I am new to VNX and just installed VNX M&R recently. The task I need to accomplish is this: management wants to know when the VNX5300 we have is starting to run into small performance bottlenecks (before it gets bad). They want a weekly report detailing some metrics that are deemed most useful for determining the "rising water" level of increasing IOPS or latency on disks/LUNs as we put more and more load on the 5300.

I know enough that a primary indicator of load is IOPS at some level of latency deemed too high (5ms on write, 20ms on read, usually) but is anyone familar enough with VNX M&R yet to know what counters I should be looking at? The counters on a LUN performance summary report for example have "response time" which is described as "The average time, in milliseconds, that a request to this LUN is outstanding, including its waiting time". This seems like the correct counter but is it accurate? The tooltip on the column says it will go status "major" at 20ms and critical at 25ms. But is this the correct benchmarks that I should be watching for? What about queue length or something else?

Thanks for any thoughts. I know there's no silver bullet answer.

Pete

3 Posts

May 29th, 2013 11:00

There are indeed useful descriptions in there. Thanks!

10 Posts

May 29th, 2013 11:00


It's been my experience that if the users aren't complaining then the numbers don't matter.  That said, when response times get around 30ms you will notice a general slow down.  At around 50ms or so, it'll seem very slow.

My advice is let the users tell you when it's slow and don't get caught up in chasing numbers for the sake of chasing numbers.

10 Posts

May 29th, 2013 11:00

If you log into the vnx, click on help, search on analyzer, click on workload characteristics, then click on performance characteristic you will find a description of the performance characteristics, and a comment.

You might find these helpful.

Response time is a good indicator.

3 Posts

May 29th, 2013 12:00

I agree with what GS said from an engineer-to-engineer perspective but this is management asking me for a report because, well, that's what they do. This is a crossing the Ts and dotting the i's thing to make management happy their investment is being looked after.

On the plus side, VNX M&R has larger interval captures going back a year so we should be able to get a good view of what's going on should we suspect something and know what counters to look at.

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

May 29th, 2013 12:00

interesting approach of being reactive. I on the other hand like to be pro-active and look at performance and make adjustments before users scream.

No Events found!

Top