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.

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

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.

github.com/mary-ext/atp... and I maintain atproto.edavis.dev/bsky-pds.txt from that repo

oh sweet thanks!!

mary's list should get you bsky's — here's my crawling script if it's any help github.com/appview-wg-b...

my relay tends to be behind on event rate for a few hours after starting, have yet to figure out why/how

my guess for this is doing all the DID resolution (PLC requests) for each new account. this slows things down when seeing lots of new accounts, which tends to happen when you first subscribe to a large PDS, but less over time

thanks! is that the same from your speedrun gist? bsky PDSs give me 400 HostNotFound…. but actually all PDSs seem to after the first 70-odd on last run. I did crank the PDS/day limit on the relay already. 🤷‍♀️

oh whoops yes it is, already forgot my own blog post that's weird though, is it coming from the pdses or your relay?

still kicking the tires before formally announcing it, but you can also use: relay1.us-west.bsky.network/xrpc/com.atp... (use the cursor param to paginate)

oh hell yes thank you i will be using this!