Yes, I got the fact it was thin provisioned.  It will make less of a difference with concatenated, but there still could be some advantage to more members, and potentially a larger advantage to using striped.  This is what is (or will be) in the latest tech note:  If the use of thin metadevices is desired in order to present larger devices to hosts, metadevices can be used. Concatenated metadevices using regular volumes have the drawback of being limited by the performance of a single metamember.  In the case of a concatenated meta comprised of thin devices, each member device is typically spread across the entire underlying thin pool, thus eliminating that drawback. Concatenated metadevices have two important operational advantages over striped metas: ·         Concatenated metadevices can be expanded without destroying existing data by adding meta members to an existing metadevice. ·         Non-metadevices can be converted to concatenated metadevices without destroying existing data.  In most cases, EMC recommends using concatenated rather than striped metadevices with Virtual Provisioning. However, there may be certain situations where better performance may be achieved using striped metas. With Synchronous SRDF®, Enginuity allows one outstanding write per thin device per path.  With concatenated metadevices, this could cause a performance problem by limiting the concurrency of writes. This limit will not affect striped metadevices in the same way because of the small size of the metavolume stripe (1 cylinder or 1920 blocks). Enginuity allows eight read requests per path per thin device. This limits the number of read requests that can be passed through to the thin pool regardless of the number of data devices that may be in it. This can cause slower performance in environments with a high read miss rate.  Symmetrix Enginuity has a logical volume write pending limit to prevent one volume from monopolizing writeable cache.  Because each meta member gets a small percentage of cache, a striped meta is likely to offer more writable cache to the meta volume. Before configuring striped metadevices, please consult with an EMC performance specialist. Caution: Striped thin metadevices cannot be expanded while preserving data.
I have to allocate a 100gig thin lun to a solaris host, will there be any diff in performance if i form a meta out of 20 members each of 5gig and meta out of 2 members(including head) each of 50gig.
thin provisioning