dnsperf | A DNS performance tool | Performance Testing library

by cobblau C Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | dnsperf Summary

dnsperf is a C library typically used in Testing, Performance Testing, Nodejs applications. dnsperf has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

Dnsperf is a single-process dns load testing and benchmarking utility. It was designed to measure the performance of your DNS Server or Local DNS Server by send a configured number of queries. Performance measures contains elapsed time, its transation rate, its concurrrency and the percentage of successful queries. These measures are reported at the end of each testing.

Support

Quality

Security

License

Reuse

Support

dnsperf has a low active ecosystem.

It has 181 star(s) with 59 fork(s). There are 14 watchers for this library.

It had no major release in the last 6 months.

There are 3 open issues and 1 have been closed. On average issues are closed in 80 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of dnsperf is current.

Quality

dnsperf has 0 bugs and 0 code smells.

Security

dnsperf has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

dnsperf code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

dnsperf does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

dnsperf releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of dnsperf

Get all kandi verified functions for this library.

dnsperf Key Features

No Key Features are available at this moment for dnsperf.

dnsperf Examples and Code Snippets

No Code Snippets are available at this moment for dnsperf.

Community Discussions

Trending Discussions on dnsperf

I have a question with option in DNSperf tool in Linux

QUESTION

I have a question with option in DNSperf tool in Linux

Asked 2020-Feb-19 at 09:30

I tried to use the DNSperf tool that is the benchmark testing tool for an authoritative name server in Linux. This tool has various features to provide the result in many aspects. But I would like to know some options like -c and -q. I tried to observe it from the source code in C. But I don't get it.

-c from the manual, it's written that

-c clients Enables the local server to act as multiple clients and specifies the number of clients represented by this server. The server sends requests from multiple sockets. By default, the local server acts as a single client.

In fact, it's just trying to send many queries as many internal threads from the source code. And the maximum of the inputted value in -c option must not exceed 256 that means the length of the socket should not exceed 256?

And two: I'm also curious about the -q option, it's written that

-q num_queries Sets the maximum number of outstanding requests. When this value is reached, dnsperf stops sending requests until either response is received or its requests time out. The default value is 100.

What is the trigger runs the number reaches 100? I don't understand about this and I tried to seek out from the source code, it's quite too complex.

Could everyone help me to understand it? I know my question is quite ambiguous, but I'm not sure how to exactly ask the right way about this so please help me.

...

ANSWER

Answered 2020-Feb-19 at 09:30

"-c" option specifies how many local source ports to use when doing queries. This is default to 1. So, you will see all queries using only one source port. Maximum value 256 means that you can use a max of 256 unique src ports to send DNS queries.

"-q" is the queue limit. There can be at most this many queries in the dnsperf queue when it stops generating new queries.

So, if the DNS server is slower than usual and takes a longer time to respond, dnsperf will only generate "-q" number of queries and wait for responses.

For example, if you set "-q" to 100, dnsperf will generate at most 100 queries and wait for their responses or timeout. If it gets 5 responses, it will generate 5 new queries, and again the queue will be full at 100. If the dns server is fast, it may happen that the queue limit of 100 is never reached, and dnsperf will make DNS queries as fast as possible.

Be aware that using a high value for -c and -q will also likely increase the memory usage of dnsperf tool in certain network conditions.

Source https://stackoverflow.com/questions/60286335

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install dnsperf

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: