DrupalCamp LA 2014 - A Perfect Launch, Every Time
0 likes579 views
The document outlines best practices for achieving a perfect launch at DrupalCamp LA 2014, emphasizing the importance of schedule, cost, and scope. It covers essential components such as team onboarding, site audits, performance tuning, and load testing, highlighting various tools for effective project management and communication. The key to a successful launch involves predefined roles, proactive checks, and thorough performance evaluations to ensure reliability and high performance.
![MySQL slow log
# Time: 130320 7:30:26
# User@Host: db_user[db_database] @ localhost []
# Query_time: 4.545309 Lock_time: 0.000069 Rows_sent: 219
Rows_examined: 254
SET timestamp=1363779026;
SELECT option_name, option_value FROM wp_options
WHERE autoload = 'yes';](https://image.slidesharecdn.com/drupalcampla2014-aperfectlauncheverytime-140908111920-phpapp02/85/DrupalCamp-LA-2014-A-Perfect-Launch-Every-Time-37-320.jpg)
![Pay attention to watchdog
6652 11/Oct 15:05 warning php Warning: Cannot modify header
information - headers already sent by (output started at /srv/
www/code/includes/common.inc:2700) in drupal_goto() (line
!
6643 11/Oct 14:21 notice php Notice: Trying to get property of
non-object in cap_ui_preprocess_page() (line 27 of /srv/www/code/
sites/all/themes/cap_ui/template.php).
!
6595 11/Oct 13:00 notice php Notice: Unknown: Can not
authenticate to IMAP server: [AUTHENTICATIONFAILED] Invalid
credentials (Failure) (errflg=2) in main() (line of ).](https://image.slidesharecdn.com/drupalcampla2014-aperfectlauncheverytime-140908111920-phpapp02/85/DrupalCamp-LA-2014-A-Perfect-Launch-Every-Time-38-320.jpg)
DrupalCamp LA 2014 - A Perfect Launch, Every Time
- 1. A Perfect Launch, Every Time DrupalCamp LA 2014
- 2. What is a perfect launch? • Schedule - On Time • Cost - On Budget • Scope - On Plan
- 3. Why should you care?
- 4. A Perfect Launch Recipe Launch Team • Onboarding Launch Check • Best Practices Load Test • Performance Tuning
- 6. How we prepare for launch Goal: Get rid of all the “uh-oh” moments Method: Launch Team Stakeholders: • Project Manager - scheduling, best practices • Developer - platform knowledge, integration • Sys Admin - responsibilities, delegation • Business owner - flawless launch
- 7. Have a system and tools Specify common workflow requirements • Repeatable tasks, delegatable Project management - Wrike, JIRA, Redmine, Trello Orientation logistics • Scheduling - calendar, deadlines • Real-time communication • Phone, Video Conference, GoToMeeting, IRC • Training - documentation, Slides, Videos
- 8. Mapping the terrain Scoping of responsibilities • Reduce confusion, set stage Channels of communication • Define emergency procedures • Issue tracking as primary inbox Staying in touch • Available, open, and regular • Proactive
- 10. Launch Check Best Practices
- 11. What is Site Audit? Drupal 7 static analysis • https://drupal.org/project/site_audit Best practices Actionable report Vendor agnostic • Optional Pantheon specific recommendations
- 12. What can an audit analyze? • Drupal caching settings • Codebase and file size • Database structure • Modules, including duplicate / missing • Non-standard code structures • Views caching • Watchdog logs
- 15. Drupal cron
- 17. Extensions (modules & themes)
- 18. Views
- 19. Watchdog
- 20. Test Configuration Simple Drupal 7 site Apache Bench • 10,000 requests to home page (5 concurrent) Warmed cache, cleared watchdog Comparison • Bad config, 1 PHP notice and warning in theme • Good config, no PHP notices or warnings
- 21. Result? Doubled performance. Performance Comparison Bad Config Good Config Load Time (min) 20:52 10:25 Requests per second 7.98 15.99 Time per request (ms) 626.192 312.780
- 23. Load Testing Performance Tuning
- 24. Why load test? Validate response times under peak load Smoke - operations under normal load Stress - behavior past peak load • Spike - short bursts Capacity - plan for growth
- 25. Who should execute load tests? Developers execute Involve stakeholders
- 26. Tools for load testing DIY and simple • Apache Bench - http://httpd.apache.org/docs/2.2/ programs/ab.html Complex / dynamic • Apache JMeter - https://jmeter.apache.org/ • Load Impact - https://loadimpact.com/ • Load Storm - http://loadstorm.com/
- 27. When should I load test? Baseline Tools • Xdebug - http://xdebug.org/ • Webgrind - https://github.com/jokkedk/webgrind • Devel - https://drupal.org/project/devel • Syslog • Watchdog • New Relic - http://newrelic.com/ Incrementally during development
- 28. Where do I perform load tests? Live environment • Bandwidth Resource limitations SaaS load testing solutions
- 29. What to expect during & after • Benchmark often • Datapoints • Aggregate • Be reasonable • Numbers should dictate expectations • Back-end • Google Analytics
- 30. Caching Opcode Cache • APC, Zend Opcache, eAccelerator Backends • Memcached, Redis, MongoDB, file system, APC Front-end caching • Varnish, Squid, reverse-proxy CDNs
- 31. Redis: Engage!
- 32. Anonymous page caching: Disabled!
- 33. Testing Varnish with cURL
- 35. PHP Slow Log
- 36. Nginx error log
- 37. MySQL slow log # Time: 130320 7:30:26 # User@Host: db_user[db_database] @ localhost [] # Query_time: 4.545309 Lock_time: 0.000069 Rows_sent: 219 Rows_examined: 254 SET timestamp=1363779026; SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes';
- 38. Pay attention to watchdog 6652 11/Oct 15:05 warning php Warning: Cannot modify header information - headers already sent by (output started at /srv/ www/code/includes/common.inc:2700) in drupal_goto() (line ! 6643 11/Oct 14:21 notice php Notice: Trying to get property of non-object in cap_ui_preprocess_page() (line 27 of /srv/www/code/ sites/all/themes/cap_ui/template.php). ! 6595 11/Oct 13:00 notice php Notice: Unknown: Can not authenticate to IMAP server: [AUTHENTICATIONFAILED] Invalid credentials (Failure) (errflg=2) in main() (line of ).
- 39. Good load test
- 40. Bad load test
- 41. Interpreting results Hard numbers Business impact
- 42. A Perfect Launch, Every Time
- 43. Thank you! Questions? @SuzanneAldrich @GetPantheon irc.freenode.net #pantheon getpantheon.com