MySQL max connection & max user connection

[javapenguin]

---

Mga brod,

Gi unsa man ninyo set inyo max connection ug max user connection sa MySQL? Mag sige mo usab depending on monitored load?

[cold_fusion]

Just set a larger value on my.cnf .

Performance should not matter much if you set it higher even the load/connections are low.
The value is just a hard limit so the server will not crawl with too much connections. This is for public servers such as in the web.

[javapenguin]

Just set a larger value on my.cnf .

Performance should not matter much if you set it higher even the load/connections are low.
The value is just a hard limit so the server will not crawl with too much connections. This is for public servers such as in the web.

In my case it's not a public server but I have optimized my program from single thread to multiple thread, as a consequence it uses more connection but performance is a lot better, for now I'ved set max connection to 500, the max user connection is still in default value, so far no one is complaining about a "too many connection error" yet.

I wonder why MySQL allows administrators to set this value if it does not have much effect in performance? We might as well set it really high.

[cold_fusion]

I wonder why MySQL allows administrators to set this value if it does not have much effect in performance? We might as well set it really high.

I think you misunderstood me.
What I mean that if you set the max connection limit to high and your user connections are low (low number of users), there is negligible impact on performance.

But if there are too many connections, the performance will be affected. That is why there is a settable limit to limit the connections and will not have effect on clients that are already connected/using the database. That is why there is a settable limit, as I mentioned at my last post, for public servers or very large user-base where hundreds or thousands of connections will occur in an instant to not affect already connected clients.

So in your case that it's not a public server, you could just set the limit to high.

[javapenguin]

I think you misunderstood me.
What I mean that if you set the max connection limit to high and your user connections are low (low number of users), there is negligible impact on performance.

But if there are too many connections, the performance will be affected. That is why there is a settable limit to limit the connections and will not have effect on clients that are already connected/using the database. That is why there is a settable limit, as I mentioned at my last post, for public servers or very large user-base where hundreds or thousands of connections will occur in an instant to not affect already connected clients.

So in your case that it's not a public server, you could just set the limit to high.

Ok, looks like I misunderstood you, my problem now with more connection is the delay in synchronization with the master server, I'm setting max connection only in slave servers which I granted SELECT (read only server). Anyway later this will be solved after I archive old data but for now I'm trying to optimize server at extreme situations.

Thanks for your reply, I also learned a lot from your previous post, I hope somebody else will share their expertise about this matter.