You can have up to 255 members in a meta, and each member on VMAX can be about 240GB in size, if you need a volume that large.
If you are using a meta volume for performance reasons on VP, up to 16 members is plenty to max out performance, and in most cases, 8 is enough.
Thanks for response.
To provide more in detail;
I am planing to provide only one metavolume/lun per filesystem to the hosts, hence in case if the filesystem needed the size more than the one thin device, i can address that using the metavolume. In case of future growth requirement i can provdie that by attaching the thin device to metavolume.
So my query was what is optimal no. of thin devices can be attached to metavolume, this is also related for growth, wherein i can draw the line about the maximum no. of tdevs in metavolume for the optimal performace resons, beyond that the host should have another filesystem.
As Quincy said, for optimal performance 8 or 16 hypers you can attach to your meta volume. With 16 hypers, you can reach up to 3.7 TB which is a good amount for most applications.
Do you really mean hypers? I think you mean devs, right? A dev is made of hypers/slices/splits.
Take a look at http://www.50mu.net/facilitate-the-conversation-say-what-you-mean-and-dont-make-assumptions/ for the correct terminology. No offence.
Size of the Hyper is really matters based on number of BackEnd Directors and FrontEnd Directors
In General VMAX 10K 8 drives per engine on 959 series
In General VMAX 10K 16 drives per engine on 987 series
Number of hypers that limit based on BackEnd Directors and FrontEnd Directors, for example if you have 2 engine 4 directors and 4 engine 8 directors, 16- way Meta 128 GB Hypers for 2 TB LUN would get you optimum performance