<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><br class=""><blockquote type="cite" class=""><div class="">On 11 Dec 2017, at 07:51, Radu Moisa <<a href="mailto:rmoisa@yahoo.com" class="">rmoisa@yahoo.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;" class=""><div class=""></div>
<div class="">Hi!</div><div class=""><br class=""></div><div class="">Thanks a lot for the hint!</div><div class=""><br class=""></div><div class="">Just so that I understand it better, nuke_limit is the "Maximum number of objects we attempt to nuke in order to make space for a object body."</div><div class="">If I set it to something like 9999999, varnish will throw out only the number of objects needed to make room for the new request, not the <span style="font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;" class="">nuke_limit</span> number of objects, right?</div></div></div></div></blockquote><div><br class=""></div><div>Yes, that's right. While trying to store an object in the cache, if not enough free space is available, Varnish will nuke up to 'nuke_limit' objects. This will happen incrementally, while the object is being fetched from the backend, stored in the cache, and eventually also being streamed to one or more clients. If the 'nuke_limit' is reached the object won't be cached and client responses will be closed (and therefore clients will end up with a truncated response).</div></div><div class=""><br class=""></div>Best,<div class=""><br class=""><div class="">
--<br class="">Carlos Abalde</div>
<br class=""></div></body></html>