I was posting on another thread, but thought this deserved its own as it is slightly different. When hosting a LimeSurvey installation, what is the best method to test the survey/server load once it is launched?
For instance, would it make sense to launch a survey then run a program like Selenium on Firefox to brute-force add responses and monitor the server during this time? That's what I did on one machine and it didn't really change the server performance during the writing of responses. I think I needed to set up multiple connections/machines at the same time and run multiple processes simultaneously to get the full effect.
Has anyone done anything like this or have suggestions? After having a server go down because too many people hit LimeSurvey at the same time, I would like to learn the best practice for testing the max survey load I can put on a LimeSurvey installation.
1. Set up a survey, with similar characteristics as the live survey
2. Fire the url from
loadimpact.com
or
loader.io
(or something similar)
3. Log into the server and monitor the situation
