On Jan 9, 2014, at 11:02 PM, Timur Irmatov <[email protected]> wrote:
> On Thu, Jan 9, 2014 at 1:27 AM, Adam W. Dace <[email protected]> > wrote: >> I can't speak to the problem of ATS losing its cache somehow, >> but as far as bandwidth usage goes you may want to try disabling this >> setting: >> >> CONFIG proxy.config.http.cache.fuzz.min_time INT 0 >> >> By default, ATS will try to pre-fetch frequently used objects. >> A neat idea, but perhaps one you don't want. > > I don't think those settings have such effect. If I am understanding > documentation correctly, those settings just give a chance to > revalidate an object that is soon to become stale when a request for > that object comes from a client. In other words, ATS would not > revalidate such objects by itself but only when clients request that > object. This means requests to origin server should be no more than > requests from clients. Yep, that is correct. It’s a way to statistically reduce the risk of a thundering herd event. For objects that gets no, or very few, requests, it should have no affect (since it never triggers). If the documentation for this setting needs updates, we’re thrilled to see patches / pull requests on docs! :-). Cheers, — Leif
