To this he were given replies from a variety of other people together with former workers and ex-CTOs of Meta and Facebook. Mike Schroepfer, “The real issue imho is they undid server side rendering and you have to download tons of code just to see a single tweet. Other countries are slow because of the round trips and initial download and not so much from the backend since everyone shares that, wrote Sam Pullara, an ex-Twitter employee. Musk replied to him in a series of tweets, saying he is wrong.
“I used to be advised ~1200 RPCs independently via a number of engineers at Twitter, which goes # of microservices. The ex-employee is unsuitable. Same app in america takes ~2 secs to refresh (too lengthy), however ~20 secs in India, because of dangerous batching/verbose comms. Actually helpful information transferred is low,” wrote Musk. “Part of nowadays will probably be turning off the “microservices” bloatware. Less than 20% are in fact wanted for Twitter to paintings!” added in another tweet. “And we will be able to after all forestall including what software a tweet was once written on (waste of display screen house & compute) underneath each tweet. Literally nobody even is aware of why we did that …” he further said.
Ex-CTO of Facebook joins in
Former Facebook executive Schroepfer also joined in. “Basic web math for @elonmusk’s claimed load time in India is 20s on account of 1200 RPC calls (vs 2s in US): Bangalore->SF is ~250ms 1200 *.25s = 5 mins! Way off!! 20s load time = MAX Reality of 80 sequential calls is most probably 5-10? 1200 is going on throughout the datacenter?, tweeted Schroepfer.
Responding to Schroeper, Musk mentioned, “Twitter is very slow in India, Indonesia & many other countries. This is fact, not “declare”. 10 to 15 secs to refresh homeline tweets is common. Sometimes, it doesn’t work at all. especially on Android phones. Only question is how much delay is due to bandwidth/latency/app.”
“There are ~1200 “microservices” server side, of which ~40 are critical to Twitter working at all, according to the server control team. Trimming down that 1200 number, reducing data usage, serialized trips & simplifying apps are all needed to improve speed of use,” Musk mentioned in any other tweet.