Every device, including meta members, has one queue per front-end slice. Only one IO in a queue can be serviced at a time. By using meta devices and mapping to multiple FAs (aka front-end slices), you provide more queues to host-facing LUNs. Using concat metas will tend to concentrate IO on a small number of the available queues, because the active LBA regions at any particular time will not be evenly distributed across all devices. By using striped metas, IO will tend to be more evenly distributed among queues... The net result is that a particular LUN will be able to do more concurrent/simultaneous IOs when it has more queues (via metas), and when IOs are evenly distributed among queues (via front-end striping).  This becomes more important when you're dealing with highly multithreaded workloads, which is very common now... Especially when you have hypervisors running multiple VMs or vmdks on a single LUN.
I know there are quite a few discussions here about this topic, however, by reading those messages, I still  could not get this question straight in my mind. I just wanted to make it clear in my own thoughts if you don't mind  1.   Is this true that in VMAX TDEV meta expansion, stripped is no better than Cancat. and then not recommended, since blocks are already striped across thin pool? 2. In some discussion, Somebody said that the difference exists in Cache operation. Since the cache is very fast to both situation, then my question is how much different would that make between stripped and cantcat.? 3.  With Enginuity 5876, what is the method to expand stripped TDEV meta device?  Thank you for your advice in advance!
In TDEV Meta expansion, stripped is no better than Cancatenated?