We are in the process of load testing our DNN solution. I thought I would post my findings to see if anyone has any comments.
· The load testing tool was deployed on a server and 5 client machines. During the testing the DBA’s traced database performance and the Virtual Machine console was monitored.
· The initial test was to simulate growth over 10 minutes to 200 concurrent users growing incrementally by 10 users every 10 seconds. This killed the machine after running for just 15 seconds (CPU maxing out at 100%).
· We then added an additional virtual processor to the VM and the same test was re-run. This time it fell over after 5 minutes of the testing period.
· A third test was then performed to simulate growth over 25 minutes to 200 users growing incrementally by 10 users every 40 seconds. This test was completed without the box falling over. However, with an average CPU usage of 80% the site was extremely slow and not of an operational standard.
· Review the test results from the various information sources in more detail to try and ascertain any conclusions on where the pinch points are.
· Performance tuning of IIS,
· Following the above, potential solutions to improve performance may become apparent. Alternatively, other options could be:
o Assign a specific processor to the VM
o HTTP compression (although from research it appears that this puts extra load on CPU so may not be an option).
o Add another virtual server and load balance between the two (although we would need to investigate if/how DNN could work in this set-up).
We could potentially have about 1000 concurrent users. The next steps above aren’t really desirable and will take time. If anyone has any thoughts or ideas be nice to hear from you.