4 ms·

I'm guessing Twitter is a highly distributed system, so of course it's doing a bunch of poorly batched RPCs. That's more or less the definition of a highly dis

by prirun 4y ago

I'm guessing Twitter is a highly distributed system, so of course it's doing a bunch of poorly batched RPCs. That's more or less the definition of a highly distributed system, where all the data can't be stored in 1 place.

dzhiurgis 4y ago
If it’s all same server then it can be batched up. Also doesn’t the new fangled http/2 protocols and the like solve this, at least partially?
- nitwit005 4y ago
  It can only be batched if the source and destination are the same. Different parts of the page likely hit different servers, and query different backends.
  - dzhiurgis 4y ago
    I really doubt they hit different servers externally
    - nitwit005 4y ago
      I phrased it poorly, but you have an http2 connection to some load balancer, and it fans out different URL paths to different services. The RPC calls are presumably done between backend services.