Simple Social Network

Fedi stats

Darius Kazemi

2y ·
Public

·
friend.camp

This content was marked as sensitive. Click to reveal

Something that can happen is:

- increase in fediverse usage
- numbers go up
- small servers crash/grind
- numbers go up more slowly since small servers are down
- unresponsive servers leads to servers that *are* up sending duplicate copies of messages at least a few times until they back off
- numbers go up fast
- bigger servers are stuck retrying lots of messages
- the retries themselves make big servers slow
- etc

I suspect this converges to stability over time though

tim 🍓

This content was marked as sensitive. Click to reveal

@darius is there a point where it is unviable to run a smaller server of any kind? is that just directly correlated to the number of external follows?

touch fluffy tail

Already, on Handholding we've had to make some changes to deal with increased load. But we're managing :flufftaker:

Mark Shane Hayden

This content was marked as sensitive. Click to reveal

@darius I suspect there is a bit of "instance churn" that contributes to this as well...

By that I mean new people who signed up for a big/general-purpose/well-publicized instance find it too slow, or has the wrong vibe or whatever decide to move instances (maybe the smaller surge back in April are now moving over during this surge? Or jsut new people instance-hopping?).

I know that instance moves can cause a brief blast of ActivityPub transactions and thus sidekiq jobs, and perhaps there are enough happening out there to make a significant contribution.

marius

This content was marked as sensitive. Click to reveal

> bigger servers are stuck retrying lots of messages

@darius isn't there a back-off strategy ? I remember being frustrated that Mastodon doesn't respect when another fediverse service returns a "405 Method Not Allowed" to signal that it does not federate, but I was hoping that after a number of tries it stops.