In a recent webinar, we shared some of the big dos and don’ts of Varnish use. After outlining the don’ts in an earlier blog post, we promised to follow up with a rundown of the five Varnish dos as presented in the webinar. Obviously, you should watch the webinar to get the full story on why and how you should take these actions in Varnish, but here’s a quick taster to give you a preview of what you’ll learn.
Over time, the most popular content we’ve created relates to hands-on Varnish use and relevant dos and don’ts. Naturally, we continue to create more content about this because our raison d’être is to help Varnish users get the maximum performance and efficiency they can from their Varnish setups.
Let’s get down to business.
Content providers often cater to global audiences when delivering streaming, news, e-commerce and gaming services. This makes tailoring content to specific locations crucial for delivering the best web experiences for their users. Being able to feed IP intelligence into content delivery operations means you can offer personalized, location-specific content experiences while managing global web traffic levels intelligently. Granular, location-based control over content delivery enables content localization, enhanced analytics and the ability to manage access and digital rights in line with national regulations and traffic patterns.
During the recent release of Varnish Enterprise 6.0.6, a significant amount of attention focused on in-process TLS.
But that’s not the only game-changing addition to the Varnish Enterprise technology stack. We now want to talk about Memory Governor, and what it means for everyone using Varnish Enterprise for streaming, web acceleration and content delivery.
Or, for those of the TL;DR persuasion: Memory Governor enables significant increases in memory availability and cache size.