Downloaded 51 times
![Rails Default Behavior
Opt-in to Edge Cache
Client
Varnish
Origin Server
Cache
$
<
<
<
curl -v https://launchpad.37signals.com/basecamp -o /dev/null
HTTP/1.1 200 OK
Cache-Control: max-age=0, private, must-revalidate
Set-Cookie: _launchpad_session=[DIGEST]; path=/; HttpOnly; secure](https://image.slidesharecdn.com/httpaccrelerationwithvarnish-140221083259-phpapp02/75/HTTP-Acceleration-with-Varnish-19-2048.jpg)
Uploaded byHarlow Ward
HTTP Acceleration with Varnish
This document discusses using Varnish as a reverse proxy and HTTP accelerator. It begins with an overview of reverse proxies and caching, then describes how Varnish handles cache hits and misses. Specific techniques covered include using HTTP headers like Cache-Control and surrogate keys to manage caching and invalidations. The document also shows how to configure Varnish using Varnish Configuration Language (VCL) and integrate it with Rails applications and services like image processing.
More Related Content
Similar to HTTP Acceleration with Varnish
HTTP Acceleration with Varnish
- 1. HTTP Acceleration withVarnish
- 2. HotelTonight Mobile-first 10k Hotel Partners 17Countries ~9M Downloads
- 3.
- 4. Overview Reverse Proxies HTTP Headers CacheInvalidation Varnish Configuration Language
- 5. Reverse proxy In computernetworks, a reverse proxy is a type of proxy server that retrieves resources on behalf of a client from one or more servers.
- 6. Request / ResponseCycle Client Reverse Proxy Origin Server www.hward.com hward.herokuapp.com (CNAME) (or IP Address)
- 7.
- 8. Reverse proxy w/ caching Webapplication accelerator.
- 9.
- 10.
- 11. Initial use ofVarnish Started with a small portion of our traffic. 33% Hits, 1% Misses, 66% Passes
- 12. The best trafficis traffic that never hits our servers.
- 13. Continue to migrateendpoints to Varnish Removed 10 EC2 XLarge Instances!
- 14. Varnish as aservice. • Dashboards and Stats • RESTful API • Killer support team (thanks Peter and Austin) • Similar pricing to Cloudfront
- 15. Fastly Point of Presence(PoP) N. America Australia Europe N. America PoPs Australia PoPs Europe PoPs Origin Server
- 16. Simulated traffic w/Loader.io
- 17. 73k req sec 1msavg. response
- 18. HTTP Headers HTTP headerfields are components of the message header of requests and responses in the Hypertext Transfer Protocol.
- 19. Rails Default Behavior Opt-into Edge Cache Client Varnish Origin Server Cache $ < < < curl -v https://launchpad.37signals.com/basecamp -o /dev/null HTTP/1.1 200 OK Cache-Control: max-age=0, private, must-revalidate Set-Cookie: _launchpad_session=[DIGEST]; path=/; HttpOnly; secure
- 20. Edge-Cache Headers Only cachepublicly accessible pages. Cache-Control Header: public, max-age or s-maxage > 0, and remove any cookies from the response. $ curl -v http://www.example.com -o /dev/null < HTTP/1.1 200 OK < Cache-Control: max-age=30, public
- 21.
- 22. max-age used on bothclient and proxy for content expiration s-maxage used only by proxy for content expiration
- 23. Cache-Control Headers for StaticAssets $ < < < < < curl -v http://www.hward.com/assets/blog-f764a70dc0ca4e7bf340d1.css HTTP/1.1 200 OK Cache-Control: public, max-age=31557600 Content-Type: text/css Status: 200 OK Via: 1.1 varnish
- 24. Cache-Control Headers for DynamicContent $ < < < < < curl -v http://www.hward.com HTTP/1.1 200 OK Cache-Control: public, no-cache, s-maxage=31557600 Content-Type: text/css Status: 200 OK Via: 1.1 varnish
- 25.
- 26. Verify cache iswarming up $ < < < < ! $ < < < < curl -v http://www.hward.com -o /dev/null HTTP/1.1 200 OK X-Served-By: cache-sv61-SJC3 X-Cache: MISS X-Cache-Hits: 0 curl -v http://www.hward.com -o /dev/null HTTP/1.1 200 OK X-Served-By: cache-sv61-SJC3 X-Cache: HIT X-Cache-Hits: 1
- 27. Cache Invalidation • Time basedexpiration • Resource based expiration • Surrogate-Keys
- 28. 1000 Requests /Minute Cache TTL Hit Ratio Origin Requests / Minute 5 sec 98.00% 20 30 sec 99.80% 2 1 min 99.90% 1 5 min 99.997% <1
- 29. 50,000 1000 Requests /Minute Cache TTL Hit Ratio Origin Requests / Minute 5 sec 99.96% 20 30 sec 99.996% 2 1 min 99.998% 1 5 min 99.999% <1
- 30. PURGE Requests Invalidate cachewith PURGE request to URL. $ curl -v -X PURGE http://www.hward.com > PURGE / HTTP/1.1 < HTTP/1.1 200 OK < Status: 200 OK < Via: 1.1 varnish {"status": "ok", "id": "68-1392243590-232248"} Note: In Production make sure to whitelist IP’s that can Purge.
- 31.
- 32. Many-to-Many Relationship Between Keysand Pages posts/1
- 34.
- 35.
- 36. Imagery Service Dynamically resizedimages for all devices. 640x260 640x900 412x 412
- 37. Initially used MagicklyGem Client Varnish Magickly Gem S3 Bucket example.com/image.jpg?resize=500x500#
- 38. Transition to ImgIX Client Varnish S3Bucket example.com/image.jpg?w=500&h=500&crop=fit
- 39. Re-write URL forbackwards compatibility with VCL
- 40.
- 41.