| Dan Luu (former Twitter employee) begs to differ: https://twitter.com/danluu/status/1591963269077819392 > An interesting thing about this claim is that not only is the implication wrong, Twitter probably has better evidence of its wrongness than any other company in its size class could have. > There are very few companies that have a better distributed tracing setup w.r.t. getting actionable insights on the backend and the ones that have a better setup are much larger (Google, FB, etc.) > Twitter client tracing also punches above its weight. > https://twitter.com/danluu/status/1267069847428411392 > Of course, the key people who did that work left or got laid off, but it's clear from the data that, if you're looking at why Twitter is so slow in, e.g., India, Uganda, etc., esp. on slow devices, tail latency comes from the network due to unreasonably large payloads + client. > When leadership wanted to drive growth in India, they were into "visionary" stuff, e.g., "add features cricket watchers would like" when the app was unusably slow [on] a low-end device and the client performance team had been disbanded. > https://twitter.com/danluu/status/1591507609651408896 |