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

[Feature suggestion] Prefetch when expired #885

Closed
alpominth opened this issue Feb 19, 2023 · 2 comments
Closed

[Feature suggestion] Prefetch when expired #885

alpominth opened this issue Feb 19, 2023 · 2 comments

Comments

@alpominth
Copy link

In Unbound, prefetching is different from Blocky, but it's useful:

       prefetch: <yes or no>
              If yes, message cache elements are prefetched before they expire
              to keep the cache up to date.  Default is  no.   Turning  it  on
              gives about 10 percent more traffic and load on the machine, but
              popular items do not expire from the cache.

/\ https://nlnetlabs.nl/documentation/unbound/unbound.conf/

An option in Block to prefetch elements in the cache when they expire would be a good idea.

In a large cache, combined with Blocky's prefetch approach would help to keep hostnames always updated.

@kwitsch
Copy link
Collaborator

kwitsch commented Feb 19, 2023

This feature is already implemented.
https://0xerr0r.github.io/blocky/configuration/#caching

@kwitsch kwitsch closed this as completed Feb 19, 2023
@alpominth
Copy link
Author

@kwitsch

Thanks, I got.

If you or another contributor could implement #833 , together with cache prefetching would make Blocky overkill.

I'm already using Blocky in production! =)

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

No branches or pull requests

2 participants