Post

dropping the pds websockets is interesting, i do wonder if this is because the PDSs arent requestCrawling this relay like they are for our relay. (the relay might have a bug and we can paper over it in our prod relay because the pds's ask us to crawl them all the time)

How does a PDS contact a specific relay with a requestCrawl? Is it configurable in the PDS Admin?

Thats a great question, i've only ever touched the relay side of this. Would be a question maybe for @divy.zone

yeah i’ll look into it more in the coming days. (i don’t have a great sense of how the pds socket is meant to be managed yet) my relay is not accessible via public inbound connections yet (though idk how a pds would even know which host it should be requestCrawl’ing to if the relay initiates)

- pds backfill is rough on this server, cpu pegs 100% - made worse by having jetstream on the same server trying to do a higher event rate - also interesting: jetstream just crashes when it’s relay websocket closes? fine if the supervisor auto-restarts it i guess.

Why would jetstream event rate be higher? Aren't the mushrooms all of the traffic, same event rate+bigger payloads?

Or is that just an artifact of this? bsky.app/profile/bad-...

- 4 shared cores on a 2017-era 2ghz epyc is not enough for a relay. could probably tune some things to get it there—seeing significant overhead from userspace networking + logging—but i def want more performance margin than this. for $5.5CAD i can get two more shared cores, or double that for 8

Run your container in host network mode, I bet 80% of that CPU is copying network packets around. Alternatively don't use a user space proxy for your container.

good news! i was wrong! with a lot of patience and many hours coaxing each individual bluesky PDS server (80 of them) to sync up, this lil relay is now up, staying up, looking happy. thanks @jaz.bsky.social + @why.bsky.team for pointers. wait,, if bsky team helps, are we even decentralizing???

this provider has a very tempting “dedicated 4 cores” offering that might work but it can’t be configured with enough storage for much of a replay window. otherwise i’m looking at ~$120/mo and that gets me a whole big real dedicated *machine*. maybe if i push for some kofi/github sponsors i could.

mostly unrelated but - i’m still not friends with docker

see, i will come back to do something with docker after a while not needing to touch it and i just do not want to have to remember things like “quotes are interpreted as literal around values in .env files” (seems this is why relay_trusted_domains and log level weren’t working)

i think i’m missing some mushrooms. jetstream emission rate is ~330/s where my prod consumer is ~520 where is the best place to get the mushroom PDS list? i went off of this page.