36
Federation Lag-o-meter (aftershock.lemmy.management)
submitted 3 years ago by to c/fediverse@lemmy.world
22 comments fedilink hide all child comments
 

I made this based on the gripe about some of the silent failures with federation. Might help users choose other servers. Might help admins troubleshoot. Open to comments and criticisms!

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 3 years ago (3 children)

When I saw the bar looking like the Burj Khalifa, I assumed it was .world instead of .ml. Interesting.

Props to Ruud@lemmy.world for dealing admirably with the Rexxit hug of death.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 1 point 3 years ago*

    I’m expecting that JSON parsing is a huge overhead with the fediverse. I work on a SAAS that needs to do all its internal processing in under 10 ms, and serializing/deserializing ends up being a sizable chunk of server time. I saw a 40% reduction in runtime using simdjson for deserializing, and there exists a rust crate for it, but I haven’t had time to look the Lemmy code over.

    Can anyone with an overloaded instance get on their command line and gather a decent flamegraph so the performance folks can aim optimizations in the right direction?

    https://github.com/brendangregg/FlameGraph

  • permalink
  • fedilink
  • source
  • parent