Trying to determine the correct queue depth for an ESXi cluster with striped TDEV meta's.

The general rule of thumb I've used is ( 8 * <# meta members> ) / <# paths to lun>

15x hosts in the ESXi cluster, 2x HBA's each (2x paths per host), each lun is a 16x striped TDEV.   Each FA have 2x ESXi clusters (30x hosts per FA port).  So 8 * 16 / 30 = 4.2 queue depth.

Because the ESX guys did some things and all the ESXi servers are now running at the defaults (32) that I didn't notice before.  The servers don't appear to have any notices of queue fulls in the ESX logs which leads me to think the hosts are not receiving queue full's on the DMX, but in SPA it looks like I've got huge queues on the FA's (the description for Queue Depth Range metric is horrible so hard to tell).  I have a pretty constant peak of 200 of AVG Queue Depth Range 7 and have spikes into the range of 8 & 9 (I'm assuming higher numbers are bad and I'm receiving lots of bursty traffic).

Nobody is yelling or screaming at us but it seems like a depth of 4 should be put back into place OR has anybody tried the adaptive queueing on ESXi (vmware KB 1008113)?  Doing a search for the configurables on powerlink (QFullSampleSize / QFullThreshold) returns nothing.  If we were to use adaptive queueing any idea as to what the values should be?  Having everything set manually is nice and predictable but it may limit throughput that adaptive might allow otherwise unavailable capacity to be used since the host won't queue up more io's.