4 ms·
Today I learned the modern browser has even more caches than I thought it did. Actually, good web engineer interview question might be how many caches there ar
by avaer 9y ago
Today I learned the modern browser has even more caches than I thought it did.
Actually, good web engineer interview question might be how many caches there are in a web request. A good interview could easily end up with 20 on the whiteboard.
- roel_v 9y agoHow do you get that high? Is that including eg cpu caches or just browser?
- throwaway2048 9y agoJust a guess on my part here, () may or may not exist . This is not a perfectly exact representation of the system, as in reality many steps here are recursively recalled, and for most steps the CPU and disk phases occur. I've certainly missed many. ( Application DNS cache) -> ( libc DNS cache ) -> ( gateway DNS cache ) -> ( DNS caching resolver cache ) -> ( DNS nameserver authoritative cache ) -> Filesystem Cache -> Hard disk Device Cache -> ( JavaScript JIT cache ) -> HTTP cache -> HTTP push cache -> HTTP Preload cache -> CPU L1 -> CPU L2 -> (CPU L3) -> ( HTTP proxy cache ) -> (N hops invoking many of these steps N times) -> ( HTTP router/relay cache ) -> ( HTTP Reverse Proxy cache ) -> HTTP Server request caching. Because on some hops almost all of them are invoked for a request, we aren't looking at 20 caches, we are looking at hundreds.
- scrollaway 9y agoEven just at the browser level, there's also the CSS cache and Image cache as well on every single page.
- deleted 9y ago[deleted]