Unsolved
This post is more than 5 years old
11 Legend
•
20.4K Posts
•
87.4K Points
0
843
August 30th, 2010 20:00
Most common performance issues you see in the field
Hello Wendy,
Since you get to see a lot of different configurations, what are the most common performance issues do you see and what do you recommend to avoid them. There are not as many knobs to tweak on the Symm as opposed to Clariion and not as easy to fix either. Please share your experience.
Thanks
No Events found!


Quincy561
1.3K Posts
0
September 2nd, 2010 11:00
The most common issue is too few resources for the workload
However that would describe pretty much every performance issue.
I think the more common issues involve not enough FA ports, disks or DA CPUs, probably in that order.
srichev
130 Posts
0
September 14th, 2010 07:00
Symm has less control compared to clariion.As per my experience,In addition to FE ports backend allocation(IOPS) if the data access pattren is highly random.V-max gives that flexibility having to create a different disk pools.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
September 14th, 2010 07:00
how does having pools in Vmax help with random workload ? If you said get EFDs ..i would agree.
srichev
130 Posts
0
September 14th, 2010 08:00
Diskpools provides required number of IOPS as opposed to shared pool where it has no control what the other apps are doing.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
September 14th, 2010 08:00
ok and how is that different from using disk groups on DMX (albeit less flexibility). You place physical drives in disk groups and create devices out of that, you can't restripe them when you add new devices to the group as you can on Vmax but the concept of isolating workload is the same.
Boom1
131 Posts
0
September 14th, 2010 12:00
we did pool testing, we get batter performance in read but not much batter in write.
yes, it is different than disk groups because you cannot balance your disk groups but you can auto balance you pool.