Fediverse

What instance is used as a reference for the delay? One you self-host (lemmy.management)?

Yes. lemmy.management. It is purposefully updating subscribed communities to as many as possible (via automation.) This doesn't correct for network lag, but the idea was to capture the "federation" lag. There's no code I'm aware of that allows admins to prioritize outbound federation traffic. I could be wrong though.

Sooo … what’s the deal with lemmy.ml … that seems to have gone beyond lag and is basically falling over … seems like the devs have neglected their own instance’s health?

I just collect the data.

What’s that Redash? Is it a plotly thing or some other product that just uses their graphing library? How have you found it?

https://redash.io I don't remember how I found it. Probably an "awesome" list on github.

Fixed! The regex was not getting content from < 0.18.0 instances. Thanks!

EDIT: I am wrong, it was something else in feddit.de's messages I THOUGHT was a version thing, but must be a localization thing. A string in the JSON was breaking some regex. Regardless.. fixed.

I didn't even load it on mobile. I will check it out tonight and maybe just create a separate "mobile friendly" dashboard.

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

Beehaw is currently doing the Burj

I am actually working on that! Stay tuned. Like days though, don't get too excited. :)

Keep in mind this is a one hour snapshot. I am working on a historical rating as well to give a better indication of overall long term stability.

Should already be able to:

https://redash.io/help/user-guide/integrations-and-api/api

For example: https://aftershock.lemmy.management/api/queries/4/results

The API key for public users is the same as the dashboard slug: oT7pdcoeHWccpvZCNmTpJKoGZND8ZdRO3wDWpMug