Hi guys-
I am using WAMP on an Asus laptop running Windows 8.1 that needs to handle a decently heavy load of users through a local network, for about 8 hours. The setup includes 11 other computers that will be hitting this server for running php scripts, such as Reading entries from a database, creating them, and updating them.
One of the apps has the potential to do 3 read entries at once as it can have 3 people on it at once. We have tested this will real users and it works for a little bit but after a while, it starts taking a while to hit the local server to check the database. It is fast again after restarting wamp ("Restart All Services" ), or even just left clicking wamp icon and doing "Apache->Test post used 8080", it's almost as if the server has stalled. Even teamviewer shows the yellow status, where it can't be connected to.... but doing the port check or wamp restart automaticaly remedies this.
The apache error log shows that the "AH00326: Server ran out of threads to serve requests. Consider raising the ThreadsPerChild setting" I raised this to 1000, it seemed to help, but I still run into the same issue eventually, So I'm not sure this is the root of the problem or not. I then raised it to 10000 and it gave me an error that the threadlimit is 1920.. Do I cahnge this mpm-conf and is it advised?
What is happening in wamp restart that allows everything to run smooth again? Can I simulate this through a script of such, also while not having the server go down? I need this server to have 0 downtime or at least minimize that as much as possible.
Also, in my php scripts I added a session_write_close() at the end of them... except for the create user scripts, I cannot tell if this helped or exactly what it does, do you think this is the culprit?
Here is the apache error log - [drive.google.com]
Any advice on how to resolve this is greatly appreciated, thank you.
EDIT- to be clear, it's not a super heavy load of users... to give an estimate for a 2-day run, we got a max of almost 500 users. It is also not a website or anything, just a server for hitting php scripts and writing reading from a database.
I am using WAMP on an Asus laptop running Windows 8.1 that needs to handle a decently heavy load of users through a local network, for about 8 hours. The setup includes 11 other computers that will be hitting this server for running php scripts, such as Reading entries from a database, creating them, and updating them.
One of the apps has the potential to do 3 read entries at once as it can have 3 people on it at once. We have tested this will real users and it works for a little bit but after a while, it starts taking a while to hit the local server to check the database. It is fast again after restarting wamp ("Restart All Services" ), or even just left clicking wamp icon and doing "Apache->Test post used 8080", it's almost as if the server has stalled. Even teamviewer shows the yellow status, where it can't be connected to.... but doing the port check or wamp restart automaticaly remedies this.
The apache error log shows that the "AH00326: Server ran out of threads to serve requests. Consider raising the ThreadsPerChild setting" I raised this to 1000, it seemed to help, but I still run into the same issue eventually, So I'm not sure this is the root of the problem or not. I then raised it to 10000 and it gave me an error that the threadlimit is 1920.. Do I cahnge this mpm-conf and is it advised?
What is happening in wamp restart that allows everything to run smooth again? Can I simulate this through a script of such, also while not having the server go down? I need this server to have 0 downtime or at least minimize that as much as possible.
Also, in my php scripts I added a session_write_close() at the end of them... except for the create user scripts, I cannot tell if this helped or exactly what it does, do you think this is the culprit?
Here is the apache error log - [drive.google.com]
Any advice on how to resolve this is greatly appreciated, thank you.
EDIT- to be clear, it's not a super heavy load of users... to give an estimate for a 2-day run, we got a max of almost 500 users. It is also not a website or anything, just a server for hitting php scripts and writing reading from a database.