wild part is that there's been zero observable difference in performance for this config change, I think it's just a difference in billing calculation.
> I think it's just a difference in billing calculation
Agree. It feels like an actuary ran some numbers and found that high I/O customers spend more on other AWS services and are more profitable than low I/0 tenants, so they changed the formula to reduce churning those high I/0 tenants.
