Performance Test Metrics for dns server performance.

[Brad Knowles]

At 5:38 PM +0100 5/9/01, Marc Thach Xuan Ky wrote:

>  To conclude, I don't believe that your results are explicable enough for
>  QA, and I think that the first thing to do is to profile the traffic in
>  more detail.

	It strikes me that instead of putting all the test results into a 
small number of categories, the tool should instead simply be 
returning all results for each query, which then get fed through the 
equivalent of a "sort | uniq -c | sort -nr", so that you can see how 
many results of which type you got, and make sure that all the 
numbers add up.  In other words, there's too much information that is 
being thrown away and not summarized in the final report.

>                The question of the "missing" queries must be answerable
>  before you can present results.  Please let us all know, I for one am
>  fascinated.

	I'm interested to see how this turns out, too.  Once we find out 
more details about the testing situation, and perhaps can get the 
test modified so as to be more transparent (with more variables 
accounted for), perhaps we'll better understand just exactly what is 
going on and why.

-- 
Brad Knowles, <brad.knowles at skynet.be>

/*        efdtt.c  Author:  Charles M. Hannum <root at ihack.net>          */
/*       Represented as 1045 digit prime number by Phil Carmody         */
/*     Prime as DNS cname chain by Roy Arends and Walter Belgers        */
/*                                                                      */
/*     Usage is:  cat title-key scrambled.vob | efdtt >clear.vob        */
/*   where title-key = "153 2 8 105 225" or other similar 5-byte key    */

dig decss.friet.org|perl -ne'if(/^x/){s/[x.]//g;print pack(H124,$_)}'