<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class=""><div class="">You can just set the inactive time longer than your possible maximum expire time for the objects then the cache manager won't purge the cache files even the object is still valid but not accessed.<br class=""></div></div></blockquote></div><br class=""><div class="">That may only have a small impact.</div><div class=""><br class=""></div><div class="">As far as I understand:</div><div class=""><ul class="MailOutline"><li class="">NGINX will remove an item only when the cache is full (ie. it needs space for a new item).</li><li class="">Items are removed based on the least-recently used (LRU) queue.</li><li class="">The least-recently-used (last) item in the LRU queue is unconditionally removed.</li><li class="">The second and third last items are removed if they are past the invalid time.</li></ul><div class=""><br class=""></div></div><div class="">The expiry of an item has no influence on the removal of items. It only affects if the item is delivered from the cache, or revalidated with an upstream request.</div><div class=""><br class=""></div><div class="">Restarting NGINX does have an impact. The LRU queue is not persisted (for performance reasons). On a restart, the LRU queue is based on the order that the cache loader finds the cached files in the file system.</div><div class=""><br class=""></div><div class="">Roger</div><div class=""><br class=""></div></body></html>