From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] namebench - dns testing tool
Date: Sun, 16 Mar 2014 12:00:27 -0700 [thread overview]
Message-ID: <CAA93jw4S-C4__E7XEYZ_cnOjWj6w2_pZdwA3EzO9X5H9d7G8tA@mail.gmail.com> (raw)
dnsmasq is now doing a few more lookups than it used to. This is a good
test to stress it out. I note that the algorithm for determining the "best"
dns server in this test is not what I'd chose - it chooses the best "average"
as near as I can tell, and the difference in performance between a local
dns server and a remote one is .8ms vs 32ms on the test I just ran - so
I'll take .8 30% of the time rather than 32ms all the time.
Still, a pretty comprehensive test, and I enjoyed watching all the
queries go by without a crash or observable memory growth in dnsmasq.
works on mac, windows, and linux (And is written in python)
https://code.google.com/p/namebench/
still looking for a high performance dnssec validation testing tool
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2014-03-16 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4S-C4__E7XEYZ_cnOjWj6w2_pZdwA3EzO9X5H9d7G8tA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox