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

Caching #12

Open
niftylettuce opened this issue Dec 5, 2019 · 4 comments
Open

Caching #12

niftylettuce opened this issue Dec 5, 2019 · 4 comments

Comments

@niftylettuce
Copy link

It would be great to have caching added somehow to reduce HTTP requests when bots spam servers.

@theel0ja
Copy link

DNS is cachable with a caching resolver, such as Unbound.

Install unbound on your server (available in most distros incl. Debian, Fedora, Arch, Ubuntu, etc.), enable&start the service and set ['127.0.0.1'] as the DNS server in options.

@silverwind
Copy link
Owner

Besides putting a caching resolver in front, you could use a in-memory cache and expire it after a fixed amount of time:

https://github.com/medikoo/memoizee#expire-cache-after-given-period-of-time

I'm not totally opposed to having a ttl-based cache in the module, but it would have to be opt-in.

@niftylettuce
Copy link
Author

Could we re-open this for TTL-based cache in module?

@niftylettuce
Copy link
Author

Or perhaps just add to the README a link to https://github.com/medikoo/memoizee#expire-cache-after-given-period-of-time?

@silverwind silverwind reopened this Aug 30, 2020
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

3 participants