<html><body><div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:13px"><div dir="ltr" id="yui_3_16_0_1_1443867388280_3639">Followin scenario:<br class="">dnsmasq runs on embedded system; many (250,000) entries like "address=/abcd/0.0.0.0/" in dnsmasq.conf<br class="">Caches in dnsmasq and browser empty.<br class="">Now, when browsing to a page with many links to other sites, page load takes more than 10sec.<br class="">Clearing browser cache, and reloading the same page, is much faster.<br class=""><br class="">Using dig on the system, running dnsmasq, I see, that first name resolution takes about 400ms.<br class="">Second try takes 0ms.<br class=""><br class="">Cache-size set to default or 10,000 makes no difference. cache-size=0 makes dnsmasq unbearable slow, looks like looping somewhere.<br class=""><br class="">Dropping the 250,000 "address=xxx" from dnsmasq.conf, shows fast name resolution (about 25ms) for first try.<br class=""><br class="">In principal, I see same effects on my faster x86-based system.<br class=""><br class=""><br class="">My conclusions:<br class="">Time for cache lookup is not influenced by number of IMMORTALs.<br class="">But creating a new entry in cache is badly effected by IMMORTALs.<br class=""><br class="">As creating a new entry assumes checking first, whether same entry exists as IMMORTAL already, which is very like a (fast) cache-lookup, this *should* not have a noticable negative effect.<br class="">Which points to a "very slow" insertion of a new entry into hash table.<br class=""><br class="">So, are my observations because of a bug or to be expected ?<br class=""><br></div></div></body></html>