The document discusses using JMeter for load testing a website. It describes creating a test scenario to emulate 400,000 users, with 10% logging in and 10% creating content. The test would check if the site's infrastructure could handle loads of 5, 20, and 50 concurrent users. The scenario would involve logging in, browsing pages, and 10% of users creating a page before logging out. The document provides tips on using HTTP requests, regular expression extractors, and other JMeter tools and recommends running tests near a production environment to avoid network issues.

1. Load Testing with
JMeter
Yuriy Gerasimov
Lead Developer

2. Emulate traffic
• authenticated or anonymous
• record the scenario
• run it locally or in cloud

3. Initial Client Requirements
• expand users base
• 400.000 users, 10% logs in
• 10% users create content
• can our infrastructure handle the load?

4. Google Analytics

5. Google Analytics
• 290 sessions peak for 1 day
• 70 sessions in 1 hour
• Average session time 12 mins
• We need to test: 5, 20, 50 concurrent users

6. JMeter Scenario
• Login
• Browse some pages (5 nodes)
• 10% of time create a page
• Logout

7. HTTP Request

8. Regular Expression Extractor

9. BeanShell PreProcessor

10. BeanShell PreProcessor

11. View Node

12. Throughput Controller

13. Pitfalls. Login cookies on redirect

14. Results Tree

15. Results Table

16. Client Report

17. Client Report

18. Client Report

19. What I would do different
• Run next to production environment (eliminate
network problems)
• Better scenarios (learn from customer exact
behavior first)

20. References, to learn
• http://www.keysolutions.com/blogs/kenyee.nsf/d6plinks/
KKYE-8LJQMG
• http://locust.io (python)
• http://tsung.erlang-projects.org (erlang)

21. Load Testing with
JMeter
Yuriy Gerasimov
Lead Developer