PS! Before i get slapped by all the Node.js guys…
- this project was done way before node.js with websockets was a reality in wappler.
- my host still don’t offer node.js on the dedicated server here in south africa… yes we went local as the server ping response was like 20ms … if we were in Europe or America… yes the AWS would have been first choice… but that is another topic for another day…
Ok the main reason im here… can somebody please explain the math to me… @Teodor
-
My site works with PHP and MySQL … not node.js
-
The maximum number of connections a single MySQL user (domain) can make to a database is set to 0 which indicates ‘unlimited’.
-
However, the maximum number of total connections across the server is set to 151
Does that mean only a 151 people can access the server concurrently??
I guess the question is… how many people can connect to the server and take part in the poll…
Only 151? or is it way more because of the opening and closing of the connections to the database.
Scenario
I created a polling app… and its using dmx-scheduler to refresh the data every 3 seconds.
There is about 30 questions on a page = 30 records from the database = 3.8kb in the console
So in a nut shell how does one work out the math to know many people can connect to the site at the same time to take part in the poll at the same time… before the server wont allow more connections…
Last updated: