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

Query caching and rate limiting #102

Open
gazwald opened this issue Aug 20, 2022 · 0 comments · May be fixed by #108
Open

Query caching and rate limiting #102

gazwald opened this issue Aug 20, 2022 · 0 comments · May be fixed by #108
Milestone

Comments

@gazwald
Copy link
Member

gazwald commented Aug 20, 2022

query commands could get expensive.

  1. Can we and should we cache query (table scan) results?

Solved by #108

  1. Alternative do we want to rate limit query commands?

Would this even work well with CNAT? Feels like premature optimisation... It'd something that needs monitoring anyway.

  1. Both 1 and 2?
@gazwald gazwald added this to the Beta milestone Aug 20, 2022
@gazwald gazwald linked a pull request Aug 23, 2022 that will close this issue
@gazwald gazwald linked a pull request Aug 24, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

1 participant