Scaling WordPress On A Small Budget
•
0 likes•1,318 views
These are the slides of a talk I presented at WordCamp Nijmegen 2018, on august 31st. In this talk I show a couple of techniques that can be used to scale a WordPress site with a severely limited budget.
Report
Share
Scaling WordPress On A Small Budget
- 1. Scaling WordPress on a small budget Brecht Ryckaert
- 2. Hi, I’m Brecht • Also known as “Bob” • WordPress Fanatic • Performance • Security • Combell
- 3. Premise • A WordPress site running on a shared server • Limited resources:
- 4. • A WordPress site running on a shared server • Limited resources: Premise A max of 25 visitors at the same time
- 6. Premise • Simulated environment on Digital Ocean • 25 Max Clients • 128 Memory Limit • Environment is running webserver and database locally
- 7. “Next month we’ll be organizing an event. Can you make sure the website can handle the extra traffic?”
- 8. “Sure, how much visitors do you estimate?”
- 9. “Not that much, I guess a couple of ten thousand per hour…”
- 11. Step 1 - Benchmarking the basic setup
- 12. Apache Benchmark • Used to simulate load • Part of Mac OSX. • Can be added via apt-get: apt-get install apache2-utils
- 13. Apache Benchmark • We’ll send 1000 sequential requests to our new WordPress site ab -n 1000 http://159.65.195.6
- 16. Apache Benchmark • We’ll now send 1000 requests to our new WordPress site in batches of 200 concurrent connections. ab -n1000 -c200 http:// 159.65.195.6
- 18. Apache Benchmark • Our shared server can process 16.98 requests per second BUT… The time required to process a single request increases from 130 ms to a whopping 11776 ms. • Now we’ll send 1000 requests to our new WordPress site in one single batch ab -n1000 -c1000 http:// 159.65.195.6
- 20. Apache Benchmark • Sending 1000 concurrent requests kills our server and takes our site down.
- 21. Scaling Up vs Scaling Out
- 22. Scaling Up (Scaling Vertically)
- 23. Scaling Out (Scaling Horizontally)
- 24. Step 2 - Database Scaling
- 25. Setting up our cluster 3 x MySQL server
- 26. Setting up our cluster https://www.digitalocean.com/community/tutorials/how-to- optimize-wordpress-performance-with-mysql-replication-on- ubuntu-14-04 Cost per droplet:
- 27. Database Scaling • 3 node database cluster • Total cost so far: 15 $ / month
- 28. Connecting The Cluster To WordPress https://wordpress.org/plugins/hyperdb/
- 29. Connecting The Cluster To WordPress Edit db-config.php to contain the various database connection strings. Place db-config.php into the same folder as wp-config.php
- 30. Connecting The Cluster To WordPress /** The name of the database for WordPress */ define('DB_NAME', 'YourDBName'); /** MySQL database username */ define('DB_USER', 'YourDBUser'); /** MySQL database password */ define('DB_PASSWORD', ‘AReallyStrongPasswordShouldBeFoundHereForSecurityReasons'); /** MySQL hostname */ define('DB_HOST', ‘mysqlserver01.brechtryckaert.com’); define(‘DB_SLAVE_1', ‘mysqlserver02.brechtryckaert.com’); define(‘DB_SLAVE_2', ‘mysqlserver03.brechtryckaert.com’); /** Database Charset to use in creating database tables. */ define('DB_CHARSET', 'utf8'); /** The Database Collate type. Don't change this if in doubt. */ define('DB_COLLATE', '');
- 31. Connecting The Cluster To WordPress Place db.php in the “wp-content” folder Remove writing permissions to db.php sudo chmod a-w /path/to/site/wp-content/db.php
- 32. Step 3 - Adding Varnish
- 33. Adding Varnish https://www.digitalocean.com/community/tutorials/how-to- configure-varnish-cache-4-0-with-ssl-termination-on- ubuntu-14-04 Cost for this droplet:
- 34. Adding Varnish Setting up Varnish: Add the GPG Key to APT: curl https://repo.varnish-cache.org/ubuntu/GPG-key.txt | sudo apt- key add - Add the repository to the sources list: sudo sh -c 'echo "deb https://repo.varnish-cache.org/ubuntu/ trusty varnish-4.0" >> /etc/apt/sources.list.d/varnish-cache.list' Update APT-GET and install Varnish: sudo apt-get update sudo apt-get install varnish
- 35. Adding Varnish
- 36. Adding Varnish https://gist.github.com/bjornjohansen/ 5448f7dd637a5bff1e8f935e693092f2 Change the default.vcl to the content of this vcl:
- 37. Adding Varnish vcl 4.0; import std; import directors; backend server1 { # Define one backend .host = “shared.brechtryckaert.com”; .port = "80";
- 38. Step 4 - Benchmarking again
- 39. VarnishWebserver MySQL 1 MySQL 2 MySQL 3
- 40. VarnishWebserver MySQL 1 MySQL 2 MySQL 3 Total Cost Of Droplets: $25
- 41. Benchmarking Again Document Path: / Document Length: 53992 bytes Concurrency Level: 1000 Time taken for tests: 8.520 seconds Complete requests: 1000 Failed requests: 0 Total transferred: 54162000 bytes HTML transferred: 53992000 bytes Requests per second: 144.59 [#/sec] (mean)
- 42. Extending upon the basic setup - HAProxy for Loadbalacing - Adding several Varnish nodes - Adding REDIS (not Memcached) nodes for object caching
- 43. Questions? Slides will be tweeted at @brechtryckaert and published on brechtryckaert.com