Drupal 10 Varnish: Optimizing Performance and Scalability

Optimizing a website's performance is crucial to ensuring a great user experience and improving search engine rankings. If you use Drupal 10, you know how powerful it can be, but also how important it is to manage its performance, especially under high traffic loads. In this article, we will explore how Varnish Cache can transform the speed of your Drupal 10 site, making it more responsive and scalable, and compare it to other solutions such as Nginx Cache.

Introduction: The Importance of External Cache

In the world of the Web, speed is everything. A slow site can turn users away and penalize your SEO ranking. Drupal 10, while a robust and flexible platform, can benefit greatly from implementing external caching systems. These systems act as an "intermediary" between your user and the Drupal server, storing copies of web pages and serving them much faster than Drupal itself, which would have to generate the page from scratch each time. This reduces the load on the server and dramatically improves response times.

Varnish Cache vs. Nginx Cache: The Key Differences

When it comes to external caching, two of the most popular solutions are Varnish Cache and Nginx Cache. Both are powerful, but they operate in slightly different ways and have distinct features, especially with regard to cache invalidation management.

• Varnish Cache: It is a HTTP proxy reverb specifically designed to speed up Web sites. It acts as an "HTTP accelerator" that sits in front of your web server (e.g., Nginx or Apache). When a request arrives, Varnish checks to see if it already has a copy of the requested page. If yes, it serves it immediately, without involving Drupal or the web server. Varnish is extremely efficient at handling a large number of concurrent requests and offers granular control over cache management through its configuration language, VCL (Varnish Configuration Language).
• Nginx Cache: Nginx is primarily a web server (like Apache), but it can also act as a reverse proxy and implement a cache. The Nginx cache is a built-in module that stores proxy server responses on disk. It is a robust and versatile solution, often used in configurations where Nginx also handles load balancing and SSL termination.

Nginx Cache: Purge Advantages and Disadvantages

While Nginx is a great solution for caching, its handling of cache invalidation (or "purge") can be more complex than Varnish.

• Vantages of Nginx Cache: It is built into the web server, which can simplify initial configuration if Nginx is already in use. It is very performant for caching static content and can be configured to handle dynamic content as well.
• Purge Advantages in Nginx: The cache purge feature in Nginx is not natively as robust as that of Varnish. To invalidate the Nginx cache programmatically (for example, when content is updated in Drupal), it is often necessary to use third-party modules or custom scripts that physically purge files from the cache directory. This can make purge automation more difficult to implement and maintain, increasing the risk of users seeing outdated versions of pages.

Varnish, on the other hand, was built with purge management in mind. It offers dedicated APIs (such as PURGE or BAN) that allow Drupal (via specific modules) to communicate directly with Varnish to selectively or mass invalidate cached pages, ensuring that users always see the most up-to-date content.

Practical Tests: Drupal 10 with and without External Cache

To understand the real impact of optimizing with external caches, let's look at some performance test results. The tests were run with ApacheBench (ab), a tool for measuring web server performance. The key values to look at are Requests per second (requests per second) and Time per request (time per request).

Testing Drupal without any external cache (only internal Drupal cache disabled for comparison)

Requests per second: 28.71 [#/sec] (mean)
Time per request: 34.836 [ms] (mean, across all concurrent requests)

Requests per second: 71.12 [#/sec] (mean)
Time per request: 14,060 [ms] (mean, across all concurrent requests)

Comment: Without any cache, response times are high (thousands of milliseconds) and the number of requests per second is low, indicating a significant load on the server for each individual request.

Testing Drupal with "Markup caching" (Drupal internal cache enabled)

Requests per second: 366.60 [#/sec] (mean)
Time per request: 2,728 [ms] (mean, across all concurrent requests)

Requests per second: 373.45 [#/sec] (mean)
Time per request: 2,678 [ms] (mean, across all concurrent requests)

Comment: Enabling Drupal's internal cache greatly improves performance by reducing response times to hundreds of milliseconds and increasing requests per second. This demonstrates the effectiveness of caching at the application level.

Testing with Varnish (without considering Drupal's internal cache for this comparison)

Requests per second: 1003.73 [#/sec] (mean)
Time per request: 0.996 [ms] (mean, across all concurrent requests)

Requests per second: 1520.97 [#/sec] (mean)
Time per request: 0.657 [ms] (mean, across all concurrent requests)

Comment: With Varnish, performance takes a significant leap forward. Requests per second exceed 1,000 and times per request drop below 100 milliseconds, demonstrating Varnish's effectiveness in quickly serving pages from the cache.

Testing with Nginx Cache (without considering Drupal's internal cache for this comparison)

Requests per second: 962.35 [#/sec] (mean)
Time per request: 1.039 [ms] (mean, across all concurrent requests)

Requests per second: 1642.55 [#/sec] (mean)
Time per request: 0.609 [ms] (mean, across all concurrent requests)

Comment: Nginx also shows excellent caching performance, with results comparable to Varnish in terms of requests per second and response times.

Testing with Nginx and "markup cache" (Drupal internal cache enabled)

Requests per second: 997.71 [#/sec] (mean)
Time per request: 1.002 [ms] (mean, across all concurrent requests)

Requests per second: 1347.54 [#/sec] (mean)
Time per request: 0.742 [ms] (mean, across all concurrent requests)

Comment: Pairing Nginx with Drupal's internal cache maintains high performance, demonstrating that both external caching solutions are extremely effective.

Test with Varnish and "markup cache" (Drupal internal cache enabled) without purge plugin

Requests per second: 676.50 [#/sec] (mean)
Time per request: 1,478 [ms] (mean, across all concurrent requests)

Requests per second: 913.62 [#/sec] (mean)
Time per request: 1,095 [ms] (mean, across all concurrent requests)

Comment: Even with the "markup cache" and without a specific purge plugin, Varnish continues to provide excellent acceleration.

Test with Varnish and "markup cache" (Drupal internal cache enabled) with purge plugin

Requests per second: 878.42 [#/sec] (mean)
Time per request: 1,138 [ms] (mean, across all concurrent requests)

Requests per second: 610.31 [#/sec] (mean)
Time per request: 1,639 [ms] (mean, across all concurrent requests)

Test Summary: The tests clearly demonstrate that the introduction of an external cache such as Varnish or Nginx leads to an exponential increase in requests handled per second and a drastic reduction in response time. This results in a much faster and more responsive Web site for users, even under high traffic loads.

Summary Table: Cache Tests and Features

Below is a table summarizing the performance test results and key features of the caching solutions examined.

*Note: "Requests/sec" and "Time/request" values have been rounded for clarity and represent an average of the test results provided. Tests with "markup cache" refer to enabling Drupal's internal cache.

Implementation of Varnish Cache with Drupal 10

Implementation of Varnish with Drupal 10 requires a few basic steps:

1. Installation of Varnish: Varnish must be installed on the server and configured to listen for HTTP requests on the standard port (e.g. 80 or 443 if you are using an SSL proxy in front).
2. Web Server Configuration (Nginx/Apache): Your web server (Nginx or Apache) will need to be configured to listen on a different port (e.g., 8080) and Varnish will forward requests to this port.
3. VCL Configuration (Varnish Configuration Language): This is the heart of Varnish configuration. You will need to write VCL rules to instruct Varnish what content to cache, for how long, and how to handle invalidation requests. Drupal provides example VCL configurations that can be adapted.
4. Drupal Modules: To integrate Drupal with Varnish and handle cache invalidation efficiently, specific modules are needed.

Purge Modules for Varnish Cache in Drupal 10

To ensure that Varnish's cache is always up-to-date and that users do not see outdated content, it is critical to implement a "purge" (invalidation) mechanism. Drupal offers excellent modules for this purpose:

• Drupal module Varnish Purge: This module provides direct integration between Drupal and Varnish, allowing Drupal to send purge requests to Varnish whenever content is modified, created, or deleted. It is a very popular and well-maintained module.
• Drupal drupal/purge: This is a more generic framework for cache purge management in Drupal, supporting several "purgers" (invalidation strategies).
  • drupal/purge_purger_http: This submodule of the drupal/purge framework allows you to send HTTP requests (such as PURGE or BAN) to Varnish to invalidate the cache. It is an ideal choice for integrating Drupal's purge system with Varnish.

Using these modules ensures that, for example, when you publish a new article or edit an existing page, Varnish is instructed to remove the old version from its cache, forcing regeneration of the page at the next access.

Benefits of Optimizing with Varnish for Drupal 10

Integrating Varnish Cache with Drupal 10 offers a number of significant benefits:

1. Increasing Site Speed: Dramatically reducing page load times, improving user experience and reducing abandonment rates.
2. Scalability Drupal Varnish: Ability to handle a much higher volume of traffic with the same hardware resources, making your site more resilient to traffic spikes.
3. Reducing Server Load: Less pressure on the web server and database, resulting in greater system stability and reliability.
4. Improving SEO Ranking: Search engines reward fast sites. A site optimized with Varnish can see an improvement in its ranking.
5. Lower Operating Costs: The ability to serve more traffic with fewer resources can lead to savings in infrastructure costs.

Useful Resources

To explore this topic further and for configuration guides, here are some useful resources:

• Drupal Varnish Project
• Varnish Drupal's Guide
• Drupal Scalability with Varnish

Frequently Asked Questions (FAQ)

D: Is Varnish Cache compatible with Drupal 10?

R: Yes, Varnish Cache is fully compatible with Drupal 10 and is one of the best solutions for performance optimization.

D: Do I have to disable Drupal's internal cache if I use Varnish?

R: No, Drupal and Varnish's internal caches work synergistically. Varnish handles HTTP-level caching, while Drupal handles application-level caching (e.g., database query or block caching). Together, they offer comprehensive optimization.

D: What is the main difference between Varnish and Nginx for caching?

R: The main difference lies in the management of cache invalidation. Varnish is designed with very efficient purge mechanisms that are easy to integrate with Drupal via dedicated modules. Nginx, while being a very good cache proxy, often requires more complex solutions for automatic and granular purging.

D: Can Varnish handle HTTPS traffic?

R: Varnish itself does not handle HTTPS traffic directly. You need to place a web server such as Nginx or a load balancer in front of Varnish to terminate the SSL connection and then forward the HTTP traffic to Varnish.

D: How difficult is it to configure Varnish for Drupal 10?

R: Initial configuration of Varnish may require some knowledge of server systems and the VCL language. However, there are many Drupal guides and modules that simplify the process.

Conclusion

Optimizing Drupal 10 performance with Varnish Cache is an investment that pays off in terms of speed, scalability, and user satisfaction. Although Nginx offers an excellent caching solution, Varnish's superiority in purge management often makes it the preferred choice for high-traffic Drupal sites. By properly implementing Varnish and dedicated Drupal modules, you can increase the speed of your Drupal and ensure a scalability that will allow you to manage the growth of your audience without compromise:

• For the Home page (/): on average, requests per second increase by about 28.11 times, or 2811%.
• For the Contacts (/contacts) page: on average, requests per second increase by about 16.87 times, or 1687%.

Do you need help with your website? Contact our expert cloud consultants, request a free consultation now!