second option is widely used in this situation  so put the hypers into the thin pool as TDATs and then create smaller TDEVs, the SRDF/S write serialization is against the TDEV and not TDAT  next question... concat or striped metas right?
We have SRDF customers that are currently running on older DMX arrays using METAS that are in increments of 8gb.   Our new VMAX array has larger drives so the HYPER sizes are 25 gb.   When im desiging SRDF i want to make sure i have as many hypers as possible due to the limit of '1 write pending per hyper' .    I have the choice of wasting storage to get the same amount of hypers or i could pool hypers ( datadevs) in to thin pool and prealloc ( thick provision) the hypers in small increments , possible the 8gb again.    Should i not worry about this because 74 code has better SRDF performance?  What are other customers doing?
SRDF write performance with Larger Lun Sizes.