[resending due to mailing list byte limits] A/B testing: Slightly off-topic - You may try separating latency effects in an A/B test by running a counter factual test. Run your feature, but don't display any changes. A/B/CF test. The experiment scorecard then would compare your feature & control to the counterfactual test highlighting indirect changes like added latency.
--justin
_______________________________________________ discovery mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/discovery
