HelioHost Posted October 23, 2017 Posted October 23, 2017 Users on Tommy should now be much less likely to see the max_user_connections error that has plagued many of you. After months of discussions with our users and testing on our accounts we have decided to increase this value. If you're account is on Johnny or Ricky and you consistently encounter this error your best course of action would be to move to Tommy. Since Ricky and Johnny have many more user accounts than Tommy the lower limit needs to be retained in order prevent one user from hogging all of the mysql connections.
miwilc Posted October 23, 2017 Posted October 23, 2017 Hmm. Will there be a more strict checking for badly written programs then? I can see the advantages of this but the abuse can ruin the server. 🤔
wolstech Posted October 23, 2017 Posted October 23, 2017 It's possible (or at least in the past it was) to get suspended for "High MySQL Load" just like it is for "High Server Load" (CPU/RAM). Abuse generally weeds itself out quite quickly on the production servers (unlike Johnny, who just bogs down from the abuse and takes forever to find resources for suspending it...)
Recommended Posts