What bringing Drupal to cloud really meant. - DrupalCon Seattle 2019
•Download as PPTX, PDF•
0 likes•37 views
We've hosted thousands of Drupal sites since Drupal was first released, but bringing the application to the Cloud meant making some key changes to how architecture was optimized. We'll discuss some of the challenges Drupal environments face and how they can be overcome by developers as hardware and architecture continue to be updated.
More Related Content
What's hot
What's hot (16)
Similar to What bringing Drupal to cloud really meant. - DrupalCon Seattle 2019
Similar to What bringing Drupal to cloud really meant. - DrupalCon Seattle 2019 (20)
More from Josh Ward
More from Josh Ward (8)
Recently uploaded
Recently uploaded (20)
What bringing Drupal to cloud really meant. - DrupalCon Seattle 2019
- 1. Subtitle Add speaker name here Title slide
- 2. Subtitle Add speaker name here Title slide Josh Ward What Bringing Drupal to Cloud Really Meant
- 3. Subtitle Add speaker name here Title slide You may know me from...
- 4. Subtitle Add speaker name here Title slide Other Drupal Stuffs (I partied with Dries at SXSW in 2009) Drupal and SEO Designing Your Drupal Site for Conversions Selling Drupal Speed Kills - Dedicated Hosting Speeds on Shared Solutions And my favorite... If you give the milk away for free they’ll buy the cow.
- 5. Subtitle Add speaker name here Title slide Or maybe you just think I’m him
- 6. Subtitle Add speaker name here Title slide In all seriousness...
- 7. Subtitle Add speaker name here Title slide In mostly seriousness...
- 8. Subtitle Add speaker name here Title slide 3 Things We Learned Bringing Drupal to Cloud
- 9. Subtitle Add speaker name here Title slide Lesson 1 PHP is a Beast (Tame the Beast) PHP Opcache (caches PHP files to execute faster) - PHP Opcache required heavy tuning for better performance. We’ve seen sizeable performance differences across multiple test and production environments.
- 10. Subtitle Add speaker name here Title slide OPCACHE Tuning Suggestions OPCACHE.MEMORY_CONSUMPTION Increase the default of 64MB to at least 512MB. OPCACHE.MAX_ACCELERATED_FILES Increase the limit from 2000 to at least 65407. This will allow more room for custom developments (especially for headless). OPCACHE.REVALIDATE_FREQ This checks for file changes but doesn’t need to be the default 2 seconds. Set to 4 instead.
- 11. Subtitle Add speaker name here Title slide Lesson 2 NGINX has the Power (Now you have it too!) NGINX (Reverse Proxy, TLS Terminator, and Microcaching) - Using NGINX as a load balancer and caching engine gives you significant performance increases while minimizing server load.
- 12. Subtitle Add speaker name here Title slide NGINX Performance Gains NGINX MICROCACHING Typically microcaching prevents high demand dynamic content from being generated more than once per second. In this use case we’re increasing the cache time to 30 seconds and only caching static content like CSS and JavaScript files.
- 13. Subtitle Add speaker name here Title slide Lesson 3 Plan for Headless (Become a master!)
- 14. Subtitle Add speaker name here Title slide Headless Thoughts 2 Things (pfft...I think we’re up to like 7) Software Collection (SCL) - CentOS repository providing a set of dynamic programming languages. Use this to manage multiple versions of of PHP or Node.JS on the same server. PHP - It’s still a thing. Don’t neglect that backend PHP.
- 15. Subtitle Add speaker name here Title slide Robbie Bailey
- 16. Subtitle Add speaker name here Title slide Join us for contribution opportunities Friday, April 12, 2019 9:00-18:00 Room: 602 Mentored Contribution First Time Contributor Workshop General Contribution #DrupalContributions 9:00-12:00 Room: 606 9:00-18:00 Room: 6A
- 17. Subtitle Add speaker name here Title slide What did you think? Locate this session at the DrupalCon Seattle website: http://seattle2019.drupal.org/schedule Take the Survey! https://www.surveymonkey.com/r/DrupalConSeattle
Editor's Notes
- My name is Josh Ward and I’ll be your substitute history teacher today.
- It’s been a while, but I’ve spent a decent amount of time in the Drupal community. I realized this week I was at my first DrupalCon at 25 (almost 10 years ago)…so I’m feeling a bit old at this point. User 652,104…if that’s still a thing.
- I’ve given a few talks you’ve probably never heard of, at Drupal events you probably have.<ist talks>, but my favorite remains If You Give The Milk…
- Or you maybe think I’m this guy, especially if you’re from Nashville or the south in general.
- In all seriousness…I voted for Pedro. A big career goal of mine was to speak at a DrupalCon. I had largely forgotten about that goal, but I’m genuine excited and grateful to be here today. My dreams have come true. I’m finally speaking at a DrupalCon!!!
- No reason to freak out here. Sys Ops, development, dev ops, etc. can be a bit overwhelming at times. It’s cool because there is definitely someone in this community ready to make it less stressful for you.
- Nexcess is a hosting company who traditionally focused on ecommerce. We learned a few things over the years and have started applying those lessons to Drupal more and more. Here are 3 things we’ve learned about bringing Drupal into the cloud.
- PHP is a beast in terms of resource usage. Especially when caching becomes more difficult with authenticated sessions. Something community and ecommerce sites have in common. Opcache helps to cache those dynamic PHP files so they execute faster.
- The first thing is just to give Opcache more resources. Our suggestion is to move from 64MB to at least 512MB. More may definitely be necessary depending on site architecture so you’ll definitely want to dial this in over time. The 2nd is increasing the limit on the number of files Opcache will handle. 65407 is seemingly random, but Opcache only recognizes prime numbers. They’re actually hardcoded into Opcache. (Yay maths) 65407 is about 5 prime numbers away from 2000 so it should be a safe limit in most cases. The 3rd is changing how frequently Opcache checks for file changes. Something that can definitely eat up even more resources as you increase the number of files you’re caching. Our suggestion is to change the default here from 2 to 4 seconds.
- Using NGINX in front of Apache gives you a bunch of advantages. You can take advantage of how powerful NGINX is while also getting some ease of use for apache. We use NGINX for many things.