Bug #101086 False Claim: When MySQL is used with the Apache Web server
Submitted: 8 Oct 2020 6:00 Modified: 8 Oct 2020 11:11
Reporter: Geert Vanderkelen Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.6,5.7,8.0 OS:Any
Assigned to: CPU Architecture:Any

[8 Oct 2020 6:00] Geert Vanderkelen
The manual states that to improve performance, the default of max_connections is set to 151 when MySQL is used with the Apache Web Server.

There are two problems with that:
* How can it improve performance?
* And why would that only have an effect with... Apache Web Server?

I know where the "Apache Web Server" comes from: the old LAMP. But Apache Server, httpd, is like something from the past.

How to repeat:
Read https://dev.mysql.com/doc/refman/8.0/en/too-many-connections.html

    The default value is 151 to improve performance when MySQL is used with the Apache Web server. 

Suggested fix:
Just say the default is set to 151, and find out a good reason why. One of them is to make sure that the system running MySQL might not get overloaded with bad, long running queries for example?
[8 Oct 2020 7:33] MySQL Verification Team
Hello Geert,

Thank you for the report and feedback.

[8 Oct 2020 11:11] Paul DuBois
Posted by developer:
Not only is there no need to mention Apache, there is no need to state (or defend) the default. The point of the section is what controls the number of connections and how to increase it. I'll remove the irrelevant text.