Skip to content
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

DNS probing performance regression in 0.19.0 #791

Closed
yegle opened this issue May 16, 2021 · 6 comments · Fixed by #796
Closed

DNS probing performance regression in 0.19.0 #791

yegle opened this issue May 16, 2021 · 6 comments · Fixed by #796

Comments

@yegle
Copy link
Contributor

yegle commented May 16, 2021

I run blackbox-exporter in docker probing a DNS server in another docker container.

With cache on DNS server end, probing latency is usually ~120us at 0.18.0. After updating to 0.19.0 it jumps to ~450us.

Knowing my patch in #724 I updated my config with preferred_ip_protocol: "ip4" since I don't configure ipv6 in my docker network, but it still result in ~200us latency.

Reverting back to 0.18.0 and now I have consistent ~120us latency again.

@karlism
Copy link

karlism commented May 25, 2021

I'm seeing similar degradation in my environment too, blackbox_exporter was updated on May 19th and since then probe_dns_duration_seconds{phase="resolve"} and probe_http_duration_seconds{phase="resolve"} has increased significantly:
image
image
All exporter VMs are running local instance of caching dnsmasq so DNS latency should be insignificant.

@SuperQ
Copy link
Member

SuperQ commented May 26, 2021

I wonder if this is related to #758

@yegle
Copy link
Contributor Author

yegle commented May 26, 2021

Presumably #758 only affects HTTP probing? It looks like the issue reported here is on DNS probing only.

@roidelapluie
Copy link
Member

The issue is with #724

I think it might be related to the fact that we now compute the hash IN the resolve phase.

@roidelapluie
Copy link
Member

Can you please test #796 ?

@roidelapluie
Copy link
Member

I will merge #796 soon but would still appreciate some testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants