The document discusses a presentation about using LoadStorm to perform load testing on websites. It provides an overview of why load testing is important for capacity planning and performance tuning. It then demonstrates how to set up a load test in LoadStorm by creating a plan, scenarios with steps, and running the test. The presentation shows the results of load tests on a Drupal e-commerce site using Amazon EC2 and Rackspace cloud servers to simulate different levels of traffic. The tests tracked metrics like response times, errors and server resource usage to help evaluate the site's performance under load.
13. How to Set up a load test - Step 1 – create a Plan
Plan is a collection of Scripts, steps and data about the tests its always the first
step and it’s the highest level
14. How to Set up a load test - Step 2 – create a Scenario
A scenario is a collection of test steps (user actions, like a click or a form submit).
Weighing (if you have more than one scenario) min/max pause and form data
set
15. How to Set up a load test - Step 2 – create a Step (and repeat)
Steps are user actions. Load storm allows for links, new pages, random clicks,
static data and form data (for required unique values)
16. How to Set up a load test - Step 3 – create a Step (and repeat)
Steps are user actions. Load storm allows for links, new pages, random clicks,
static data and form data (for required unique values)
18. The Servers – Amazon EC2 Small and Medium VS RS Cloud 2G and 4G
19. EC2 Small: Peeked at 75
users
• User Load and Requests
per second
• Average Response time
• Peak Response time
• Error rate %
20 to 115 users in 40 minutes
20. Result: RS peeked at 65
users
• User Load and Requests
per second
• Average Response time
• Peak Response time
• Error rate %
20 to 115 users in 40 minutes
21.
22. While running load tests, what’s happening on the server? Apache is consuming all
resources, its actually not the database.
23. Result: EC2 Medium
Peeks at 75 users again
Random Server Fail
– test needs to be
restarted
20 to 115 users in 40 minutes
24. Result: EC2 Medium
Peeks at 75 users again
• User Load and Requests
per second
• Average Response time
• Peak Response time
• Error rate %
20 to 115 users in 40 minutes
25. Result: RS 2G, keeps
going at 115
• User Load and Requests
per second
• Average Response time
• Peak Response time
• Error rate %
20 to 115 users in 40 minutes
26.
27. While running load tests, what’s happening on the server? Apache is consuming all
resources, its actually not the database.
Promet Source Chicago Drupal Meet Up presentation – Using Load Storm
Objectives: - Learn when and why to stress test your site - Learn how to use load test with load storm
Promet Source is a Chicago based full service Web Development Company focusing on open source technologies to build complex websites and web applications. Promet has used Drupal to develop solutions for Fortune 100 companies, start-ups & non-profits. Promet uses Drupal to build a broad variety of websites, web applications, and has most recently, used Drupal to assist in its Mobile Application Development.Along with their Drupal expertise Promet Source differentiates themselves by providing a superior customer experience throughout all facets of the development process, including design, software engineering, project management, quality assurance as well as hosting & online marketing services.Promet Source areas of Drupal expertise:- Drupal Web Development- Web Application Development- Mobile Application Development- eCommerce Web Development- Member Management Web Development- Web Design- Chicago Web Hosting- Chicago Online Marketing
Load testing is NOT front end performance testing It is also not High Availability analysis
What is Load Storm:LoadStorm has been awarded and recognized as the Best Load Testing Tool byWebhostingsearch.com, the leading provider of best quality web hostingreviews on the Internet.“LoadStorm™ is a web-based load testing tool for simulating what users do with a web site or web application. You use it to build tests that send requests to your server in the same way that a user's browser sends requests to your server. But these tests are executed by our automated systems rather than by a user, so they can be done repeatedly and in large numbers simultaneously. They can also be built using our tool in such a way as to simulate a large number of different users with different tasks to perform.
Our test site isOptionIt a drupal 6 ecommerce site built by Promet Source
The OptionIt home page has 44 objects on it
How to Set up a load test - Step 1 – create a Plan Plan is a collection of Scripts, steps and data about the tests its always the first step and it’s the highest level
How to Set up a load test - Step 2 – create a ScenarioA scenario is a collection of test steps (user actions, like a click or a form submit). Weighing (if you have more than one scenario) min/max pause and form data set
How to Set up a load test - Step 2 – create a Step (and repeat)Steps are user actions. Load storm allows for links, new pages, random clicks, static data and form data (for required unique values)
How to Set up a load test - Step 3 – create a Step (and repeat)Steps are user actions. Load storm allows for links, new pages, random clicks, static data and form data (for required unique values)
Here is our example scenario
We will be load testing the same site installed on four instances: - Amazon small - Amazon mediumVersusRack Space Cloud 1024MB RamRack Space Cloud 2048MB Ram
Stress Test results on a drupal site on Amazon small instance
Stress Test results on a drupal site on Rack Space Cloud 1024G instance
Comparative number of users registered on RackSpace cloud server versus Amazon EC2 small
New Relic view of Process memory and CPU usage on RackSpace cloud server during the stress test