You are most welcome jmudad206. Appreciate if you can mark any of the answers as "Answered" if you really feel your question is answered [IMAGE]  This will help our community moderators a lot.   Hope it helps Mohammed Salem [NAME]
All, I have been reviewing many of the size recommendations for tdev meta members.  Recently I recieved an analysis and briefing from and EMC Engineer that suggested that we use meta member sizes that are multiples of 4 and 8.  He suggested meta members be 4, 8, 16 or 32 because of the physical architecture of the VMAX.  This made sense because of 8 engines, 4 processors per director, 8 processors per engine, 4 or 12 backend directors per engine depending on the engine and daisy chaining of cabinets.  This was to even out the workload across the backend more evenly.  In the reading I have done so far Quincy56 and others are stating that the power of 2 or multiples of 4 or 8 do not apply with virtual provisioning.  So just to be clear, the current VMAX design and backend architecture has nothing to do with tdev performance or number of meta members?  Even though the architecture is all based on even numbers and multiples of 4 meta devices can be 4, 5, 6, 7, 10, 11, 13, 15, 19, members and it doesn't matter except for the meta count against the FA processor?  Thanks for your input.
tdev meta members for large luns