You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by GitBox <gi...@apache.org> on 2022/02/18 00:52:54 UTC

[GitHub] [trafficserver] mlibbey commented on issue #8672: What's the point of ttl-in-cache ?

mlibbey commented on issue #8672:
URL: https://github.com/apache/trafficserver/issues/8672#issuecomment-1043685773


   The RAM cache is tightly related to the disk cache. The way I think of it is that a disk object gets popular enough to be nominated to be represented in ram -- if its not on disk it can't be in ram cache.
   
   FWIW(eg, not answering your question), we don't use cache.config. Instead, we use header_rewrite plugin to add/set Cache Control on a per remap basis -- like 
   
   ```
   # ignore the origin CC, just use ours
   cond %{READ_RESPONSE_HDR_HOOK} [AND]
   cond %{HEADER:Cache-Control} ="" [AND]
   cond %{STATUS} >199 [AND]
   cond %{STATUS} <400
       set-header Cache-Control "max-age=300, public"
   ```
   or 
   ```
   # use origin CC if present, otherwise use ours
   cond %{READ_RESPONSE_HDR_HOOK} [AND]
   cond %{HEADER:Cache-Control} ="" [AND]
   cond %{STATUS} >199 [AND]
   cond %{STATUS} <400
       set-header Cache-Control "max-age=21600, public"
   ```
   
   Also not answering your question... think a few orgs have found LRU to be more performant for ram cache than CLFUS.
   


-- 
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: issues-unsubscribe@trafficserver.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org