cached

One would have a cached answer to a problem if the circumstances and question were identical, i.e.

And the JS and images are probably cached anyway, since they don't change like the rest of the design.

The other part is that different nodes will have cached the URL you're requesting at different times.

Which, of course, makes fetching data blazingly fast, thanks to how filesystems are already handled and cached by the OS.

Our physical read replicas receive redo log records, update cached entries and have readonly access to the underlying storage tier.

I'd expect in-lining the css to be a slight net loss once the data is cached - my strategy would be a `style-<md5sum>.css` with a long max-age.

Everything cached, static html pages, simple design and the big one: no tracking cookies/tracking scripts.

I think all the database is cached in RAM.

With the style.css fully cached, I'm getting ~15ms faster on the sideband approach than with inline styles.

You run a thousand different micro-benchmarks on the performance difference between re-binding a cached method handle for a setter, or just calling instance_variable_set.

Isn't it reasonable to assume most users already have a CDN version of adsense and facebook cached since 90% of all websites use it?

I assumed that this was a long running experiment, getting Google to reindex a new cached version between every test.