<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">Em 04/03/2015, à(s) 09:42:000, Bob Harold <<a href="mailto:rharolde@umich.edu" class="">rharolde@umich.edu</a>> escreveu:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><pre class="" id="comment_text_28">(In reply to Patrick McManus [:mcmanus] from <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1093983#c22" class="">comment #22</a>)
<span class="">> ((In reply to <a href="http://bugzilla.mozilla.org/" class="">bugzilla.mozilla.org</a> from <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1093983#c21" class="">comment #21</a>)
> > This whole thing is about getting TTL for in-Firefox caching, right?
>
> yes - each time we look at this we do need the cache because the the number
> of names that are looked up in the browser (most of them speculatively)
> tends to overwhelm the os cache. I'd be happy to look at data in a separate
> bug to revisit, of course.</span>
Can someone be more specific on what "overwhelm"s the os cache? I assume all the names still need to be looked up in te os and thus get in the os cache. Is it cache hits that are too many - that sounds unlikely. Or is it entries with very low ttl that you are caching longer in the browser to avoid lookups?</pre></div></div></blockquote><br class=""></div><div>It's not just the OS cache. A good number of home routers do not implement recursive caching at all, forwarding all queries to an ISP recursive server. Those recursive servers will now see twice the load as before. </div><div><br class=""></div><div>Rubens</div><div><br class=""></div><div><br class=""></div><div><br class=""></div><br class=""></body></html>