20 is plenty if your pages run fast enough. Excess clients after MaxClients are queued in Apache. If the 20 are consuming resources (eg cpu/disk) it is better to queue the excess than to have everybody stumbling over each other. In MySQL, the excess clients beyond max_connections are give an error.
> -----Original Message----- > From: Reindl Harald [mailto:h.rei...@thelounge.net] > Sent: Monday, March 18, 2013 12:15 PM > To: mysql@lists.mysql.com > Subject: Re: How to change max simultaneous connection parameter in > mysql. > > > > Am 18.03.2013 19:26, schrieb Rick James: > > If you are running Apache with MaxClients set too high, that can > cause the problem. > > "too high" is relative > > > That Apache setting should be something like 20. (Other web servers > > have similar settings.) > > 20 is a laughable value as long you are not hosting only sites with no > users at all > > i have seen "MaxClients 500" be critical while the hardware was not > overloaded and we had THOUSANDS of users which liked to get the website > with all it's images, no way with stupid settings of 20 which means > only ONE USER at the same time can fetch a single page with images and > stylesheets > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
