Read on Twitter
At some point, we& #39;re choosing where to place the user& #39;s low quality (compared to cloud) connection. The worseness is due to flakiness, higher latency, and lower bandwidth.
Moving requests to Mighty& #39;s lower latency and higher bandwidth cloud is transformative - if you& #39;ve ever downloaded a file while SSH& #39;d into EC2, it& #39;s a magical feeling. Everything can be loaded near-instantly. Then add aggressive caching, ML-driven pre-loading/optimization, etc.??
Connection flakiness is the main thing that could now degrade experience at time-of-flakiness (vs. time-of-load).
But I suspect for a large (and rapidly growing) % of users, the experience of Mighty will be better overall in spite of that dynamic.
But I suspect for a large (and rapidly growing) % of users, the experience of Mighty will be better overall in spite of that dynamic.
Impact of cloud rendering, de/serialization and mega CPU/GPU usage is possibly even bigger. There& #39;s some interesting extreme things that could be done to optimize/cache/pre-compute components of these operations when doing it at scale, too.
Some interesting concerns expressed in this tweet & parent tweets of this thread: https://twitter.com/Jonathan_Blow/status/1387530112959057920">https://twitter.com/Jonathan_...
