mlibbey commented on issue #9526: URL: https://github.com/apache/trafficserver/issues/9526#issuecomment-1472848591
- ATS fills its cache when serving requests. So, if a client asks for `https://tiles.example.com/foo` and ATS has never seen a request for /foo, it will be a cache miss. But, the next time it should be a hit (though, in reality... it depends -- cache-control max-age time; disk size; amount of content to be cached; etc) - In the screeny, so far, the cache is only 31.7GB/160.9GB full. You'd expect it to grow to have both numbers identical over time... and the cache hit percentage will also likely grow - By default, the entire url is used as the cachekey -- including query parameters (and order matters). Since you are getting cache hits, seems like things are set up reasonably correctly. You can test by fetching an object (that has proper Cache-control headers), then fetching again adding the header "Cache-control: only-if-cached" eg, `curl -H "Cache-control: only-if-cached" ...` it will give an http error status code if its not in cache. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
