These tests (especially unconstrained versions) can get very
backlogged and may take a while to finish. We sometimes flake waiting
for that. This is not hazardous (IMO), as the scripts that run these
tests already have timeouts to make sure that these don't truly go on
forever.
2. Make the time spent in the benchmark phase actually be
benchmark_seconds rather than benchmark_seconds-warmup_seconds
as it is currently.
tsan documentation says 2-20x, so set it at 20x
asan documentation says 1.2-2.7x, so set it at 3x
msan documentation says 2-4x, so set it at 4x
This is now much less optimistic than before
2. Reactive tsan tests for qps_test
3. Set CPU load for qps_openloop_test
4. Divide qps_openloop_test Poisson rate by the slowdown factor of
the configuration
Craig Tiller