Re: Understanding Total QPS from named stats
At Tue, 25 May 2010 07:48:48 -0700 (PDT), ivan jr sy wrote: > As a follow up question, the stats "queries resulted in successful > answer" - does this counter only cover queries that were answered > with DNS data? See the BIND 9 ARM (http://www.isc.org/files/arm96.html#statistics_counters). To quote the relevant part: Queries resulted in a successful answer. This means the query which returns a NOERROR response with at least one answer RR. > how about DNS queries that where the responded with SERVFAIL, > NXDOMAIN, timed-out due to delegation, dropped, or non-successful > answers - should those be included to the Total QPS as well? There's no simple answer to this question. If you use a relatively naive tool like queryperf, it measures qps based on any responses regardless of the RCODE. But if the server returns a response with SERVFAIL because it's too busy to handle all incoming queries (rather than, e.g. it was due to a bogus response from an external authoritative server), you wouldn't like to include those responses to measure the effective performance of the server. On the other hand, if a query results in "dropped" or "duplicate", no response is sent to the client, so a tool like queryperf would consider this a "lost query" (although "duplicate" isn't likely to happen with queryperf). However, it may not make sense to exclude "dropped" queries because it doesn't mean the server loses the query with its performance problem. So, again, there's no simple answer. But, in general, I think you can get a reasonable measurement of performance even if you include (or incorrectly exclude) these questionable cases. --- JINMEI, Tatuya Internet Systems Consortium, Inc. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Understanding Total QPS from named stats
Jinmei - Thank you. As a follow up question, the stats "queries resulted in successful answer" - does this counter only cover queries that were answered with DNS data? how about DNS queries that where the responded with SERVFAIL, NXDOMAIN, timed-out due to delegation, dropped, or non-successful answers - should those be included to the Total QPS as well? > > > 4692675534 queries resulted in successful > answer > > "queries" are a subset of "requests" only for messages with > opcode = > query. These are probably what you want to look at in > this context. > ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Understanding Total QPS from named stats
At Thu, 20 May 2010 19:37:34 -0700 (PDT), ivan jr sy wrote: > But is there a best practice in calculating it from the named stats? > > Can the dynamic updates, notify and such be considered as queries? In named.stats you copied, no: > 5818360608 IPv4 requests received "requests" mean all incoming messages from client, including dynamic update requests and notifies. > 4692675534 queries resulted in successful answer "queries" are a subset of "requests" only for messages with opcode = query. These are probably what you want to look at in this context. If all you need is to just count the number of incoming queries, you can see it in the "Incoming Requests" section of the stats: ++ Incoming Requests ++ 54708 QUERY 1592 UPDATE --- JINMEI, Tatuya Internet Systems Consortium, Inc. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Understanding Total QPS from named stats
Hi Bind Users, Good day. I wish to know what is the industry standard when dealing with the "TOTAL QPS" and how do we calculate this with BIND? My understanding of "QPS" is the queries that a DNS server has received regardless if it was dealt with a successful response, nxdomain or timed-out due to lame. But is there a best practice in calculating it from the named stats? Can the dynamic updates, notify and such be considered as queries? There are several monitoring systems, load balancers and the like that monitors Total QPS from a DNS server registered in the system. I wish to create an in-house script to calculate the same way. I got a two instances (with 1 minute differential) sampling of rndc stats of two DNS caching servers. Thank you. The first take showed the following ++ Name Server Statistics ++ 5818360608 IPv4 requests received 4463 IPv6 requests received 16627 requests with EDNS(0) received 213523 TCP requests received 709406 auth queries rejected 10280592 recursive queries rejected 10 update requests rejected 5700295060 responses sent 1165166 truncated responses sent 16627 responses with EDNS(0) sent 4692675534 queries resulted in successful answer 137516372 queries resulted in authoritative answer 5469041736 queries resulted in non authoritative answer 339189 queries resulted in referral answer 199466607 queries resulted in nxrrset 77252124 queries resulted in SERVFAIL 714076778 queries resulted in NXDOMAIN 980927690 queries caused recursion 86311171 duplicate queries received 31745639 queries dropped 10990123 other query failures a minute later... ++ Name Server Statistics ++ 5817893991 IPv4 requests received 4463 IPv6 requests received 16627 requests with EDNS(0) received 213516 TCP requests received 708839 auth queries rejected 10279493 recursive queries rejected 10 update requests rejected 5699834173 responses sent 1165099 truncated responses sent 16627 responses with EDNS(0) sent 4692279730 queries resulted in successful answer 137507789 queries resulted in authoritative answer 5468595382 queries resulted in non authoritative answer 339185 queries resulted in referral answer 199450131 queries resulted in nxrrset 77248026 queries resulted in SERVFAIL 714034125 queries resulted in NXDOMAIN 980871535 queries caused recursion 86305506 duplicate queries received 31745639 queries dropped 10988457 other query failures ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
