Fascinating research. Any thoughts, AWS friends?https://twitter.com/dvassallo/status/1120171727399448576 …
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
they're based of years of lessons on the best customer exoeriences. E.g. I think the burst capacity on start is correlated with better experience for software fetches.
The goal of fairness algorithms is to be unseen. Benchmarks that sit on send obviously hit them, but we'd hate customers with real work loads to have to think about them, and perf goes up silently with every rev of our Nitro updates.
Ideally this should be transparent just like for the T2/T3 burst CPU credits allowing people to buy extra capacity after they consumed all their credits.
I think I found the statement that drives the rotor blades of Uber's new electric helicopters.
Oh you literally work at AWS. From your website "I’ve worked at Amazon Web Services since 2008."
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.