Post

fig (aka:[phil])
@bad-example.com

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

fig (aka:[phil])@bad-example.com

kinda still a relay noob but uh i think it’s doing the thing non-us jurisdiction (montreal) non-us-company-cloud-provider relay. chillin.

Why
@why.bsky.world

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)

fig (aka:[phil])
@bad-example.com

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)

0 reposts4 likes

Why
@why.bsky.world

yeah, for now the PDSs just have a hardcoded value that is the relay they want to make sure sees them. it should be configurable per PDS, but its not meant to just ask any relay that exists (theres not really a discovery system there)