RobinHood dynamically allocates cache space to those backends responsible for high request tail latency (cache-poor) backends, while stealing space from backends that do not affect the request tail latency (cache-rich backends). In doing so, Robin Hood makes compromises that may seem counter-intuitive (e.g., significantly increasing the tail latencies of certain backends).
Tag: caching
HTTP Proxy Considerations
very good summary. performance, features etc
Stale Cache Handling
The other issue we had was when services go down. In many cases, it’s preferable not to show users a “hard” error, but instead to use slightly stale content, if it’s available. Stale-if-error allows you to do this — again, in a way that’s controllable by you.
i like the stale-if-error in particular
Browser Cache Usage
40-60% of Yahoo!’s users have an empty cache experience
huh? wow. i wonder how we as an industry can do better.
S3CDNFilter
phil writes a servlet filter to make CDN via S3 a snap. too many acronyms?
Detecting 304
And to feed consumers, while supporting these headers can save you bandwidth, computing a hash on the content may save you processing time.
i can confirm that 😉
michael radwin on web caching
Michael Radwin knows what he is talking about: Caching and Cache-busting for Content Publishers. highly recommended.