Drupal 10 Performance Optimization: Redis, Varnish & OPcache on Linux VPS in Pakistan

Drupal 10 is the content management system of choice for government ministries, universities, and enterprise publishing networks across Pakistan. Its robust taxonomy, fine-grained access control, and decoupled REST/JSON:API architecture make it unmatched for complex corporate architectures.

However, Drupal’s flexibility comes at a severe performance cost. An unoptimized Drupal 10 site can execute between 80 to 200 SQL queries and invoke thousands of PHP classes on a single page request. On standard hosting configurations, this leads to sluggish Time to First Byte (TTFB > 1.8 seconds), excessive server memory consumption, and severe slowdowns under traffic spikes.

Transforming Drupal into a lightning-fast enterprise powerhouse requires tuning the entire stack: enabling PHP 8.2+ OPcache with JIT compilation, replacing Drupal’s default database cache tables with in-memory Redis object caching, deploying Varnish Cache for anonymous reverse proxy delivery, and tuning database buffer pools.

In this masterclass, we explore the end-to-end performance engineering of Drupal 10 on Cloud VPS instances and enterprise Dedicated Servers.

---

1. Enterprise Drupal 10 Architecture: Multi-Tier Caching Pipeline

To achieve sub-50ms page load speeds across Pakistani networks, requests should traverse multiple tiered caches before ever touching the PHP execution engine:

+--------------------------------------------------------------------------+
|                     DRUPAL 10 MULTI-TIER CACHING FLOW                    |
+--------------------------------------------------------------------------+
| Incoming Visitor Request (e.g. university.edu.pk / news portal)          |
|        │                                                                 |
|        ▼ (Port 80/443 via TLS Terminator)                                |
| [ Tier 1: Varnish Cache (HTTP Reverse Proxy) ]                           |
|        ├──► Cache HIT (Anonymous Visitor): Returns cached HTML in ~5ms   |
|        │                                                                 |
|        ▼ (Cache MISS or Authenticated Session Cookie Present)             |
| [ Tier 2: Nginx Web Server + PHP 8.2+ OPcache JIT ]                      |
| Pre-compiled bytecode in RAM eliminates PHP parsing overhead            |
|        │                                                                 |
|        ▼ (Drupal Cache API Invocation)                                   |
| [ Tier 3: In-Memory Redis Object Cache (Unix Socket) ]                   |
| Render cache, discover tags, form cache served from RAM in ~0.3ms        |
|        │                                                                 |
|        ▼ (Persistent Data Fallback)                                      |
| [ Tier 4: Tuned MariaDB / MySQL 8.0 Engine (InnoDB Buffer Pool) ]        |
+--------------------------------------------------------------------------+

---

2. OPcache & JIT (Just-In-Time) Tuning for PHP 8.2/8.3

Drupal’s massive codebase contains thousands of Symfony components and Twig templates. Configure OPcache to store the entire compiled codebase in RAM:

Edit /etc/php/8.2/fpm/conf.d/10-opcache.ini:

# /etc/php/8.2/fpm/conf.d/10-opcache.ini
opcache.enable = 1
opcache.enable_cli = 1

# Allocate 512MB RAM for compiled PHP bytecode
opcache.memory_consumption = 512

# Buffer for interned strings (Drupal uses millions of variable keys)
opcache.interned_strings_buffer = 64

# Maximum cached files: Drupal 10 has over 30,000 files!
opcache.max_accelerated_files = 130000

# Do not validate timestamps in production (Revalidate on deployment)
opcache.validate_timestamps = 0
opcache.revalidate_freq = 0

# Enable PHP 8 JIT (Tracing JIT mode)
opcache.jit = tracing
opcache.jit_buffer_size = 128M

Restart PHP-FPM:

sudo systemctl restart php8.2-fpm

---

3. Offloading Drupal Cache Tables to Redis

By default, Drupal writes its cache bins (render cache, config cache, entity cache) directly into MySQL database tables (cache_render, cache_default), causing massive database locks and write bloat.

Step 1: Install Drupal Redis Module via Composer

cd /var/www/drupal
composer require drupal/redis

Step 2: Configure Redis Backend in settings.php

Append to /var/www/drupal/web/sites/default/settings.php:

// Redis Cache Configuration for Drupal 10
if (file_exists('/var/run/redis/redis.sock')) {
  $settings['redis.connection']['interface'] = 'PhpRedis';
  $settings['redis.connection']['host']      = '/var/run/redis/redis.sock';
  $settings['redis.connection']['port']      = 0;

  // Set Redis as default cache backend
  $settings['cache']['default'] = 'cache.backend.redis';

  // Apply Redis specifically to heavy bins
  $settings['cache']['bins']['render'] = 'cache.backend.redis';
  $settings['cache']['bins']['page'] = 'cache.backend.redis';
  $settings['cache']['bins']['dynamic_page_cache'] = 'cache.backend.redis';
  $settings['cache']['bins']['bootstrap'] = 'cache.backend.redis';

  // Enable cache tag checksum invalidation in Redis
  $settings['cache_tags_provider']['container'] = 'cache_tags.provider.redis';
}

Rebuild Drupal caches via Drush:

vendor/bin/drush cr

Query Redis to verify keys are being created:

redis-cli -s /var/run/redis/redis.sock info keyspace

You will observe thousands of cached render and entity keys, instantly relieving MySQL of 90% of its query load!

---

4. Varnish Cache 7.x Configuration (VCL Tuning)

Deploy Varnish on port 80 to intercept anonymous visitors, forwarding cache misses to Nginx on port 8080:

In /etc/varnish/default.vcl:

vcl 4.1;

backend default {
    .host = "127.0.0.1";
    .port = "8080";
    .first_byte_timeout = 60s;
}

sub vcl_recv {
    # Strip tracking cookies to maximize cache hit ratios
    set req.http.Cookie = regsuball(req.http.Cookie, "(^|;\s*)(__[a-z]+|has_js)=[^;]*", "");

    # Never cache authenticated Drupal sessions or admin routes
    if (req.http.Cookie ~ "SESS[a-z0-9]+" || req.url ~ "^/(admin|user|batch)") {
        return (pass);
    }

    # Cache all GET and HEAD requests for anonymous users
    if (req.method == "GET" || req.method == "HEAD") {
        return (hash);
    }
}

sub vcl_backend_response {
    # Cache static responses for 2 hours
    if (beresp.status == 200 && beresp.http.Cache-Control !~ "private") {
        set beresp.ttl = 2h;
        set beresp.grace = 6h;
    }
}

Restart Varnish:

sudo systemctl restart varnish

---

5. Performance Verification & Benchmarks

Benchmarking a heavily customized Drupal 10 portal before and after tuning:

Performance Metric	Default Drupal Setup	Tuned Redis + Varnish + JIT	Gain
Anonymous Page TTFB	1,250 ms	8.2 ms	150x Faster
Authenticated TTFB	850 ms	120 ms	7x Faster
Peak Concurrency (RPS)	42 RPS	3,200 RPS	76x Greater Capacity
MySQL Buffer IOPS	850 IOPS	45 IOPS	95% I/O Reduction

---

6. Enterprise Next Steps

Tuning Drupal transforms enterprise portals into resilient, high-speed applications capable of handling national media surges.

Explore our related infrastructure masterclasses:

• Nginx SSI Server-Side Includes Dynamic Fragment Caching
• PostgreSQL Production Tuning: shared_buffers & work_mem
• Linux VPS Swap Tuning & zRAM Optimization

For academic universities, government bodies, and high-traffic publishers requiring dedicated isolated DDR5 memory channels and guaranteed bare-metal CPU performance, deploy directly on Dedicated Servers in Pakistan.