Great point. Per my example above, we might only discover that "64ms kinda sucks", not that "an additional 32ms on top of the original 32ms kinda sucks".
And who knows, maybe after a "kinda sucky valley" there's some comfy-feeling region up above 250ms, where the "float" just feels okay. :)
And who knows, maybe after a "kinda sucky valley" there's some comfy-feeling region up above 250ms, where the "float" just feels okay. :)