pull down to refresh
26 sats \ 5 replies \ @tomlaies 20 May 2022 \ on: Daily discussion thread
I'd be interested in how "busy" the SN backend is? If you look at stdout or something are the logs just racing through almost unreadable? Or like every few seconds? e.g. how often is the backend sending out a login e-mail? Because I do every few days.
I hope this isn't a weird question, I'm just interested in the reality of tech at this scale. Are you looking things like this up with very specific SQLs (because I'd for sure do that all the time)?
We have about 150 requests per second hitting the servers last I checked as reported by the load balancer.
I have slow logs to try to surface slow things and a bunch of dashboards about server memory, CPU usage, request latency, network download/upload, etc.
reply
150 per second?! That's surprising. Damn.
reply
Yeah, there's quite a bit of polling for user balance changes and other stuff.
reply
I often have multiple tabs open, each of those making 1QPS (even when not in focus), so it adds up.. Since the page has around 15 active users at a time, I think multiple folks do the same with multiple tabs open.
Is the higher QPS causing any notable issues or is it fine for now?
reply
It appears to be fine. It occupies the db a bit, given some of the queries are expensive (eg looking for replies of replies), but I see that more of a query optimization problem than a request/second problem.
reply