approach on parsing the query-log file

Jonathan Petersson jpetersson at
Tue Apr 28 18:04:42 UTC 2009

Just realized something else, since I'm using perl in this case it's
going to be a permament bottleneck regardless of wether I use
syslog/tcpdump/querylog, it just isn't quick enough for that kind of

Back to the drawing-board


On Tue, Apr 28, 2009 at 10:49 AM, Jonathan Petersson
<jpetersson at> wrote:
> I don't think the cost is that great having querylogging enabled,
> running the same test using dnsperf there's a 43% performance-increase
> but 70 000 queries per second is still acceptable with query-logging
> enabled.
> /Jonathan
> On Tue, Apr 28, 2009 at 10:05 AM, Alan Clegg <Alan_Clegg at> wrote:
>> Jonathan Petersson wrote:
>>> So I gave tail a try in perl both via File::Tail and by putting tail
>>> -f in a pipe.
>> As was stated previously in this thread, you are going down a bad path
>> by using query-log for any purpose beyond short debugging sessions.
>> The loss in performance is rather painful.
>> The use of a network sniffing package is much preferable.
>> [Just to see, try running your million queries with and without query
>> logging turned on and see if you are happy with the results]
>> But, if that's what you want to do, I wish you luck.
>> AlanC
>> _______________________________________________
>> bind-users mailing list
>> bind-users at

More information about the bind-users mailing list