DNS lookup are not cached about cacheable-lookup HOT 3 CLOSED

@sarthakgithub I am not an expert, but it sounds to be working correctly from your description.

The lookup event means an actual DNS enquire is performed, so looking at the timing of those won't give you an average reduction unless the DNS server is overwhelmed.

It should give you a great reduction on the count of those, as they are just not performed, which sounds to be confirmed by your "'lookup' event is not getting fired".

Am I missing something?

from cacheable-lookup.

https://runkit.com/szmarczak/6216f010c015ea00080b7dbe

[some big number]
0 [or 1]

As you can see it takes some time to get the first response, but the next one is cached. lookup is getting fired but much faster than usually.

https://runkit.com/szmarczak/6216f103768a8c000a2d21a2

Try uncommenting the install call. As you can see, without that - it takes ~15ms as it performs another DNS call. With that included - there's no wait.

from cacheable-lookup.

@sarthakgithub Unless you provide more details on your issue, I see no problem here.

from cacheable-lookup.