3 ms·
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.
by fosterfriends 3y ago
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.
- avisser 3y ago> 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.
- jacobegold 3y agoThis feels likely!
- EwanToo 3y agoOur commit latency dropped when we turned it on, so _something_ changed on a technical level