We have performance issues with our VMAX on the linux servers. I can see from SPA that the write respose times are in between 17-22 ms for about 300 to 400 iops. I lookedd at the FA ports should i consider %busy to see if there is a bottleneck at the ports?? what else should i look to find out the reason and also
I have .ttp files from vmax which are 2 hrs interval fies for a day is there a way to make those 12 files(1day) into 1 file(1day). I have a STP navigator to open these files.??
And what is Symmerge used for compared to STP navigator??
There is probably too many variables to solve the problem here. I suggest that you get customer service involved. Could be some of the IOs are larger than 256k. If so, you should find a way to reduce the IO size. Also could be IO bursts, or not enough logical devices or FA paths if RDF/S.
Yeah there could be many things involved here i suspect that the io sizes are about 256kb.
But From SPA how to determine that the FA is over utillized. should i look for %busy
And i have ECC performance manager data and STP data from vmax i analyse using STP navigator but find very different statistics for both data can you tell me which would be more accurate(performance manager or Stp DATA)??
STP and ECC can only monitor IO rates at 1 minute samples, you may have write bursts that happen for a few milliseconds, then stop. This can lead to very high utilizations for very short periods of time, and idle other times. SPA should be the best method to monitor the system.
SymmMerge is used to calculate utilizations, but still is relying on data at 1 minute samples.
I would look at your queues at the host level. If you are seeing high queues with short samples, say 5 seconds, I would suggest adding more FAs or devices.
Quincy561
1281 Posts
668
0
Posted March 5th, 2011 08:00
There is probably too many variables to solve the problem here. I suggest that you get customer service involved. Could be some of the IOs are larger than 256k. If so, you should find a way to reduce the IO size. Also could be IO bursts, or not enough logical devices or FA paths if RDF/S.