The deck can be found by searching the EMC World website for VMAX Performance.  The 5% is the WP limit for a Symm device.  If you make a meta with 4 members, it can consume 20% of writable cache.  You won't have any WP issues as long as the write rate to cache is slower than what the disks and the DAs can keep up with.  So it depends on the speed of the disk, the number of disks, and the number of DA CPUs if they are the bottleneck. If you see the slides I mention, I compare the results from one device to multiple devices on one FA.  More devices gives more performance.  As long as you have multiple devices active, you will get the best performance.  Those charts are cache operations and have NOTHING to do with the backend disks at all.
Hi All,  I have 30 Servers which are of  40 TB each and We need to migrate them to the VMAX from Clariion. The migration would be done from the host side. Below are some questions that I am lloking for answers.  What is the Difference If I give 40X1TB compare to assigning 400X100GB Luns. When the IO Goes into the VMAX Cache the destaging happens to the meta which basicaly stripped across meta members. How Does large lun count help oracle and other databases help for the host for the performance when IO goes directly into Cache.  If I have like 1 TB Cache on VMAX the lun count and Size of the Lun should not be concern on the vmax as the IO goes into the Cache.  Is there any IOPS limit per TDEV and TDAT after which we see WP pending count.  Any Help would be appreciated.               
VMAX Write Workload diff with small number of lun vs larg number of lun count