Erik Webb discusses key considerations for load testing Drupal 8 websites, including that users do not need to know it is built with Drupal, the importance of testing different user paths and backend operations, new caching features in Drupal 8, and ensuring load tests accurately model expected traffic patterns rather than simply extrapolating results. Load testing is important to evaluate a site's performance and scalability under varying user loads.
14. So you tested your homepage?
Source: https://www.flickr.com/photos/striatic/2135057566/
15. So you tested your homepage?
Source: https://www.flickr.com/photos/striatic/2135057566/
16. Testing User Paths
User Checkout
User A logs in.
User A visits product page X.
User A adds product X to their
shopping cart.
User A visits their shopping cart.
User A enters payment information.
User A completes transaction.
User Search
User B visits the homepage.
User B enters “product X” into
the search box.
User B views search results
page.
User B clicks on a random
search result.
21. Backend Operations
Does saving content affect performance?
What affect does a deployment have on live traffic?
Do cron jobs affect web traffic?
Background content sync
External web services
22. New “Side Effects” in Drupal 8
Headless Drupal
Caching by default
Cache tags
Service containers
We don’t know yet.
Source: https://www.flickr.com/photos/27762949@N00/33602814/
24. Request Fuzzy Math
Number of Threads/Workers
Ramp-up Period
Iterations
Expected Max Concurrency =
Total Requests
Avg. Response Time × Test Length
25. Throughput Shaping Timer
Simply provide requests per
second for each time period
Matches how traffic is usually
measured
jmeter-plugins.org
Supported by Blazemeter