-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adgaurd Limit Concurrent requests per second #7463
Comments
here is the config file
|
The problem is in dnsproxy root@cr-srv-st:~/test1# dnsperf -s 127.0.0.1 -p 5355 -c 1 -d test/query.txt -n 10 [Status] Command line: dnsperf -s 127.0.0.1 -p 5355 -c 1 -d test/query.txt -n 10 Statistics: Queries sent: 70200 Response codes: NOERROR 70200 (100.00%) Average Latency (s): 0.003816 (min 0.000183, max 0.028328) |
how does dnsmasq, powerdns and unbound compare? |
I get over 70K request per second on my self developed dns server also I get much more on dnsmasq and unbount, please tell me what can I do to increase the speed It's not using hardware resources, I have enough cpu and ram |
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Linux, AMD64 (aka x86_64)
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
latest
Action
Just benchmark the adguard and you will see it won't go higher than around 27K Query Per Second
Expected result
around 50K or 100K per second at least
Actual result
around 26K per second
Additional information and/or screenshots
There is no There is no hardware limit, all good all ok, Please tell me what can I do ?
I even set max goroutine to 1500, but no difference
Please tell me what can I do ?
here is test results of my own dns server ( upstream of adguard )
The text was updated successfully, but these errors were encountered: