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

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.

- 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

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.

yeah several things could work, several more steps between here and making enough commitment to start figuring that out :)

0 reposts4 likes

postgres on the same host (nvme), persist dir on network storage (SAN i think?) lenient sync validation otherwise all defaults from the repo dockerfile. podman, for some reason, which is why i ended up with userspace networking (oops)

okay, im gonna have to try out running the new code and see where the perf is getting eaten, it shouldnt be that expensive to do all that

one thing I can think of is that you should probably add the bsky PDS domain to TRUSTED_DOMAINS, otherwise they get throttled. maybe I should make that the out-of-box config

oh yeah yes i do have that too, RELAY_TRUSTED_DOMAINS="*.host.bsky.network" but i’m *pretty sure* i had my environment messed up when i requestCrawled the mushrooms because they all got the default low limit, so i did manually fix each one. maybe a web admin control over a default config for it?