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

dnsdist: set backend server selection policy to chashed to optimize cache usage #158

Merged
merged 1 commit into from
Mar 20, 2024

Conversation

DasSkelett
Copy link
Member

@DasSkelett DasSkelett commented Mar 14, 2024

Set the backend server selection to chashed, which concentrates queries for the same domains from any dnsdist to the same recursors, improving the cache usage on the recursors.

The documentation recommends to set the weights between 100-1000, with 100 the distribution was a bit imbalanced, with 500 it is good (see first screenshot).

Here are a few monitoring screenshots showing the effects: (The first day shown having the old wrandom active, then two days with chashed, and then back to wrandom)

While on average the incoming requests to the recursors stayed roughly the same:

image

The outgoing queries decreased a bit:

image

The response times decreased a bit:

image

And the packet cache & recursor cache hit ratio increased:

image

While (recursor) cache size decreased:

image

https://dnsdist.org/guides/serverselection.html

@DasSkelett DasSkelett requested a review from a team as a code owner March 14, 2024 20:07
@GoliathLabs GoliathLabs merged commit e0f592f into freifunkMUC:main Mar 20, 2024
4 checks passed
@DasSkelett DasSkelett deleted the dnsdist-chashed branch March 24, 2024 20:47
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 this pull request may close these issues.

2 participants