How to handle massive traffic on a WordPress site

With massive traffic comes a bulk load of request that will stress out your server.

So how do you serve requests without causing much load on your server?

One word: Caching

Caching may sound easy. But it isn’t.

“There are only two hard things in Computer Science: cache invalidation and naming things.”

— Phil Karlton

WordPress doesn’t need to send real time data to its users, that’s why most of the requests at MySQL, php, webserver level can be cached.

Throughout your WordPress app, you can find various levels of cache such as:

  1. Browser cache (http headers)
  2. RAM Object cache (Memcached, Redis)
  3. Public cache (config via webserver)
  4. Private cache (config via webserver)
  5. DNS cache (Cloudflare)
  6. OP cache (zend)
  7. OS cache (Linux)
  8. MySQL cache (indexes and cache tables)

I have prepared a cheatsheet on how you can configure fine tune your sever to serve 30,000 requests per second (around 500 active users) very easily on a digitalocean droplet at affordable costs. Find the link to download below:

Cheatsheet

Related Posts
Leave a Reply

Your email address will not be published.Required fields are marked *