pull down to refresh

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