Re: dnscache performance still applicable today?

Matthew Dempsky wrote:
> On Sun, May 24, 2009 at 10:56 AM, Rihad <[email protected]> wrote:
>>  PID USERNAME    THR PRI NICE   SIZE    RES STATE  C   TIME   WCPU COMMAND
>> 45536 Gdnscache     1  48    0   481M   479M select 0  24:00  6.15% dnscache
> 
> On most SMP systems I've used, 6.15% here means 6.15% of one CPU, not
> of all CPUs.
> 
Yeah, you're right, don't know why I said that... So it's even less than 
50% loaded.
CPU load isn't the problem anyway.

>> I don't think
>> dnscache can do multiple requests concurrently under current design.
> 
> It can and does. :)
> 

Really? And request completions are being notified using signals, or 
what? I see that dnscache is only linked to libc.so, no threads, no 
nothing. Sorry, I believe you, this isn't really my turf  ;-)


Let's please not forget where it all started:
2009-05-24 18:42:48.254665500 stats 2098047 158736598 190 0
that 190 "queries that dnscache has received via UDP but not yet 
responded to or dropped".


I'll wait and see if someone complains at slower web browsing due to DNS 
delays.