…which is OK, because one of the points of MySQL is to be easy to use, and that it’s accessible even if you don’t know what you’re doing. The problem is that in the interest of saving money and because things work “well enough” people don’t have the expertise they need.

It would be like going to a ‘learning’ doctor or dentist all the time — sure, you can save money, but if you have anything other than standard issues (ie, not just a regular healthy visit, shots, or an ‘easy’ issue like pink eye or the flu) then you want someone with experience.

innodb_file_per_table: I agree, but some disagree.

“But really, these settings are easily found in a basic audit” — that’s my point exactly. If any basic audit should reveal that the defaults haven’t been changed and that they should be — then the problem is with the defaults.

innodb_file_per_table should default to being set on; it’s appropriate for probably 99% of the cases out there.

max_connections limit of 151 is ridiculous. The only reason to have max_connections is so you don’t crash due to trying to use too much memory. So instead of crashing you block access, which results in the same problem — customers don’t see data.

But really, these settings are easily found in a basic audit, and I’d almost rather have these so you can tell that a server hasn’t really been looked at, versus ‘it’s been looked at and the defaults are good’.