Django中的性能，负载和压力测试

Question

I am studying the different types of testing for a Django application. I know how to do functional and unit testing in Django and how to apply different methodologies, but now I am facing a new challenge, I need to know how to do:

• Performance testing
• Load testing
• Stress testing

I know the difference between them but I dont know which is the best methodology to follow,which are the best packages for do it or simply where I can get some documentation about it.

So my question is, how can I start to do these types of tests in a Django app or where can I get some good documentation about it?

Thanks

Answer 1

Load Testing and Stress Testing are basically performance testing sub-types where:

• Load testing: is putting the system under anticipated load to see whether performance metrics like response time or throughput match expectations/ SLA s
• Stress testing: is determining system boundaries and/or bottlenecks, ie you start the "normal" load test and increase the load until monitored metrics exceed acceptable thresholds or errors start occurring (whatever comes the first)

Also be aware of Soak Testing - when you put the system under a prolonged load to see if it is capable of handling sustained concurrent usage. The majority of bottlenecks are being discovered during Soak Testing phase.

---

With regards to "how do I":

1. First of all you need a performance testing tool. Given python and django tags my expectation is that you find Locust tool interesting as you will be able to write your tests in some form of Python language. You can also consider Grinder where you can write tests in Jython (Java bindings for Python) language so you won't have to learn the new tool from scratch. Other free and open source load testing tools are listed and compared in the Open Source Load Testing Tools: Which One Should You Use?

2. Next step will be creating a load test scenario. You need to mimic real application usage as close as possible, to wit you need to properly simulate real user using real browser with all related stuff like:

   • cookies
   • headers
   • cache
   • think times
   • AJAX requests
   • embedded resources handling (images, scripts, styles, fonts)
3. Once you have the test and have the confidence regarding it is doing what it is supposed to be doing you can run it with increased number of users and see how does you application behave under the load, correlate increasing/decreasing load with changing metrics/resources usage