Post

learned so far: - 4 cores seems _enough to run_ but on this particular host it’s kind of marginal. 16GB ram seems plenty. - it’s been dropping pds websockets, and doesn’t seem to recover on its own. not sure why. - bandwidth is less than i was expecting. - +jetstream on this server is too much

- 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.

- 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

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???

full-scale indie atproto relay is live and public! get yer non-bluesky-owned firehose here! relay.fire.hose.cam jetstream soon, i’ve just done enough nginx iptables for one day.

how do i add this to my pds

looks like it got your pds already! it’s connecting to all the online PDSs it can based on mary’s scraping: github.com/mary-ext/atp...

i meant like is there a way i can connect my pds to it in some way (along with the official relay)

ohh ok i saw some kind of relay thing in the same properties file i used to configure the email stuff so i thought you could use that to connect to the relay in some way