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

Optimize matcher creation in stores #6333

Open
fpetkovski opened this issue May 4, 2023 · 1 comment
Open

Optimize matcher creation in stores #6333

fpetkovski opened this issue May 4, 2023 · 1 comment

Comments

@fpetkovski
Copy link
Contributor

Is your proposal related to a problem?

Creating regex matchers in stores is currently quite expensive, at least according to a Receiver CPU profile. We have a lot of alerting and recording rules, so query throughput is fairly high.

image

Describe the solution you'd like

We could pool matchers or use some sort of an LRU cache to avoid the massive churn caused by high query RPS.

Describe alternatives you've considered

N/A

Additional context

@bwplotka
Copy link
Member

bwplotka commented May 4, 2023

👍🏽 Help wanted!

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

Successfully merging a pull request may close this issue.

2 participants