Drupal commerce performance profiling and tunning using loadstorm experiments drupal mid camp chicago 2014
Download as PPTX, PDF3 likes4,036 views
This document outlines the stress testing and optimization of a Drupal Commerce system on a LAMP stack, detailing objectives such as performance improvement and results measurement. It includes descriptions of load testing methodologies, test scenarios, and key performance metrics, emphasizing the importance of site speed for user experience and business profitability. Additionally, it presents various configurations and choke points encountered during testing, suggesting caching and reverse proxy implementations to improve performance.
![Test Plan
Script #3 Activity (User abandons a cart, requires login) (68% [2])
1. VUser hits homepage
2. VUser logs into an existing customer account
3. VUser goes to category #1
4. VUser goes to product #2 in category #1
5. VUser adds that product to her cart
6. VUser removes that product from her cart
7. VUser logs out
8. End of session
Script #4 Activity (User purchases a product, requires login) (3% [1])
1. VUser hits homepage
2. VUser logs into an existing customer account
3. VUser goes to category #1
4. VUser goes to product #3 in category #1
5. VUser adds that product to her cart
6. VUser reviews cart
7. VUser goes through the checkout process
8. VUser receives order confirmation
9. VUser logs out
10. End of session](https://image.slidesharecdn.com/drupalcommerceperformanceprofilingandtunningusingloadstormexperiments-drupalmidcampchicago2014-140331103009-phpapp01/85/Drupal-commerce-performance-profiling-and-tunning-using-loadstorm-experiments-drupal-mid-camp-chicago-2014-18-320.jpg)
Drupal commerce performance profiling and tunning using loadstorm experiments drupal mid camp chicago 2014
- 1. Promet SourceMidCamp 2104 Stress testing and optimizing a Drupal Commerce on a LAMP stack
- 2. Objectives •Stress Test Drupal Commerce on a standard server •Make a performance improvement •Measure results & Repeat •How to look at stress test results •Which improvements made the biggest impact What You’ll Learn
- 3. AboutAndy • @AKUCHARSKI • PROMET SOURCE FOUNDER • @PROMETSOURCE
- 4. AboutPromet •Focus on Drupal •CMS platform •Web applications •Systems integration •Practice areas •Agile Development (Scrum, Kanban) •DevOps (cook with Chef) •Support (cover 24x7) •Mobile (build native apps) •Founded in 2003 •Global team •30+ “Prometsters”
- 5. What Load Testing is not http://www.flickr.com/photos/peterlozano •Front End Performance Testing •High Availability Analysis
- 6. Why Load Test • Capacity Planning • Capacity Testing • Performance Tuning
- 7. Why care about performance? Google Blog: 2011 – “We encourage you to start looking at your site’s speed— not only to improve your ranking in search engines, but also to improve everyone’s experience on the Internet. “ • Time = Money… • Speed = Money… • Slower Page load = Less Money
- 8. HTML DELAY EXPERIMENT Determine impact of server delays GOAL Delay before sending HTML page Different experiments with different delays Small % of traffic Monitor negative impact METHODOLOGY
- 11. •LoadStorm.com is a load testing tool for websites • Test scenarios such as login, e-commerce • No scripting language needed • Run large tests up to 500,000 concurrent users • No download, no install, no servers to buy
- 12. Waterfall diagrams •X = Time •Y = Number of objects on page •Y(1) = HTTP Request – rest of objects are elements of the page, images, CSS and js files, etc, etc. •Time to load all elements
- 13. •DNS Lookup – time it takes for browser to find the server •Initial Connection – three way handshake, hard to control •Time to First Byte – server wait time •Content Download – how long it takes to transfer the data from server to browser
- 14. • Back End • Front End • Render Start • Render complete
- 15. The Victim – 37 objects on home page
- 17. Test Plan Script #1 Activity (User browses anonymously) (11%) 1. VUser hits the homepage 2. VUser goes to category #1 3. VUser goes to product #1 in category #1 4. VUser goes to category #2 5. VUser goes to product #2 in category #2 6. VUser goes to category #3 7. VUser goes to product #3 in category #3 8. End of session Script #2 Activity (User browses after logging in) (10%) 1. VUser hits the homepage 2. VUser logs into an existing customer account 3. VUser goes to category #1 4. VUser goes to product #1 in category #1 5. VUser goes to category #2 6. VUser goes to product #2 in category #2 7. VUser goes to category #3 8. VUser goes to product #3 in category #3 9. VUser logs out 10. End of session
- 18. Test Plan Script #3 Activity (User abandons a cart, requires login) (68% [2]) 1. VUser hits homepage 2. VUser logs into an existing customer account 3. VUser goes to category #1 4. VUser goes to product #2 in category #1 5. VUser adds that product to her cart 6. VUser removes that product from her cart 7. VUser logs out 8. End of session Script #4 Activity (User purchases a product, requires login) (3% [1]) 1. VUser hits homepage 2. VUser logs into an existing customer account 3. VUser goes to category #1 4. VUser goes to product #3 in category #1 5. VUser adds that product to her cart 6. VUser reviews cart 7. VUser goes through the checkout process 8. VUser receives order confirmation 9. VUser logs out 10. End of session
- 20. Target
- 21. Choke Point – around 100 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Baseline
- 22. Choke Point – around 100 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Baseline
- 23. Choke Point – around 100 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Baseline
- 24. Choke Point – around 100 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Baseline
- 25. Choke Point – around 100 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Baseline
- 26. Choke Point – around 100 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Baseline
- 27. Choke Point – around 300 users • Standard LAMP Stack • Drupal Commerce • Drupal Cache On Drupal Cache!
- 28. Choke Point – around 100 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on D.Cache
- 29. Choke Point – around 300 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Drupal Cache!
- 30. Choke Point – around 300 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Drupal Cache!
- 31. Choke Point – around 300 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Drupal Cache!
- 32. Choke Point – around 300 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Drupal Cache!
- 33. Choke Point – around 350 users • Standard LAMP Stack • Drupal Commerce • Drupal Cache On + CSS + JSC Aggregation D.Cache + Agg
- 34. Choke Point – around 100 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on D.Cache + Agg
- 35. Choke Point – around 350 users • Standard LAMP Stack • Drupal Commerce • Drupal Cache On + CSS + JSC Aggregation D.Cache + Agg
- 36. Choke Point – around 350 users • Standard LAMP Stack • Drupal Commerce • Drupal Cache On + CSS + JSC Aggregation D.Cache + Agg
- 37. Choke Point – around 360 users • Standard LAMP Stack • Drupal Commerce • Drupal Cache + Views Cache Views Cache
- 38. Choke Point – around 100 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Views Cache
- 39. Choke Point – around 360 users • Standard LAMP Stack • Drupal Commerce • Drupal Cache + Views Cache Views Cache
- 40. Choke Point – around 360 users • Standard LAMP Stack • Drupal Commerce • Drupal Cache + Views Cache Views Cache
- 41. Choke Point – around 450 users • Standard LAMP Stack • Drupal Commerce • Drupal caching • Reverse Proxy Reverse Proxy (nginx)
- 42. Choke Point – around 100 users • Standard LAMP Stack • Drupal Commerce Kickstart out of the box, no caching turned on Reverse Proxy
- 43. Choke Point – around 450 users • Standard LAMP Stack • Drupal Commerce • Drupal caching • Reverse Proxy Reverse Proxy (nginx)
- 44. Choke Point – around 450 users • Standard LAMP Stack • Drupal Commerce • Drupal caching • Reverse Proxy Reverse Proxy (nginx)
- 45. Choke Point – around 450 users • Standard LAMP Stack • Drupal Commerce • Drupal caching • Reverse Proxy Reverse Proxy (nginx)
- 46. Choke Point – around 450 users • Standard LAMP Stack • Drupal Commerce • Drupal caching • Reverse Proxy Reverse Proxy (nginx) LIVE DEMO
- 47. Pt_query_digest
- 48. Pt_query_digest
Editor's Notes
- #12: 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.
- #16: The OptionIt home page has 44 objects on it
- #20: We will be load testing the same site installed on four instances: - Amazon small - Amazon mediumVersusRack Space Cloud 1024MB RamRack Space Cloud 2048MB Ram
- #21: We will be load testing the same site installed on four instances: - Amazon small - Amazon mediumVersusRack Space Cloud 1024MB RamRack Space Cloud 2048MB Ram
- #22: Stress Test results on a drupal site on Amazon small instance
- #23: Stress Test results on a drupal site on Amazon small instance
- #24: Stress Test results on a drupal site on Amazon small instance
- #25: Stress Test results on a drupal site on Amazon small instance
- #26: Stress Test results on a drupal site on Amazon small instance
- #27: Stress Test results on a drupal site on Amazon small instance
- #28: Stress Test results on a drupal site on Amazon small instance
- #29: Stress Test results on a drupal site on Amazon small instance
- #30: Stress Test results on a drupal site on Amazon small instance
- #31: Stress Test results on a drupal site on Amazon small instance
- #32: Stress Test results on a drupal site on Amazon small instance
- #33: Stress Test results on a drupal site on Amazon small instance
- #34: Stress Test results on a drupal site on Amazon small instance
- #35: Stress Test results on a drupal site on Amazon small instance
- #36: Stress Test results on a drupal site on Amazon small instance
- #37: Stress Test results on a drupal site on Amazon small instance
- #38: Stress Test results on a drupal site on Amazon small instance
- #39: Stress Test results on a drupal site on Amazon small instance
- #40: Stress Test results on a drupal site on Amazon small instance
- #41: Stress Test results on a drupal site on Amazon small instance
- #42: Stress Test results on a drupal site on Amazon small instance
- #43: Stress Test results on a drupal site on Amazon small instance
- #44: Stress Test results on a drupal site on Amazon small instance
- #45: Stress Test results on a drupal site on Amazon small instance
- #46: Stress Test results on a drupal site on Amazon small instance
- #47: Stress Test results on a drupal site on Amazon small instance
- #48: Stress Test results on a drupal site on Amazon small instance
- #49: Stress Test results on a drupal site on Amazon small instance
- #50: [email protected]@akucharski@prometsource