The discussion revolves around implementing an adaptive “server too busy” page in Discourse. geoff777 suggests that Discourse could prioritize server resources by closing connections to inactive anonymous users when the server is overloaded, eventually limiting access to members only. watchmanmonitor questions whether it’s better to upgrade hosting or limit user access. geoff777 responds that upgrading may not be feasible for small forums, and an adaptive system could encourage sign-ups. DJ_Lobster agrees, suggesting a feature similar to those used by Reddit, Twitter, and Imgur when they reach their limits, which would be beneficial for those with limited server resources.
Could Discourse be self-aware of the load on system resources?
If an instance was beginning to slow or be overloaded by users, could Discourse begin closing connections?
First anonymous users not active for say 30 minutes.
Then 15 minutes - 10 - 5 … then make the forum viewable by members only if the server was really busy?
In a nutshell. Prioritising server resources in favour of active/logged in users.
I wonder… better to get a stronger host or drive away would-be users?
Are you offering to pay?
Of course throwing bucketfuls of cash into excess cores and memory is fantastic but for people running small forums in the minimum droplet. The next option is double the price.
It could be unexpected traffic.
On a cold wet November evening when your site suddenly gets 25% more users than at anytime before.
This might be a useful feature. Members first. It could encourage sign up.
