Logql benchmark and performance improvement. #1371
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello !
This PR adds a benchmark for the LogQL engine and also improve allocations and therefore cpu usage when doing metrics queries. Improvement is around 40% in term of CPU and 80% for allocation/memory usage.
I can see there is still ways to improve metrics queries, but I didn't wanted to change the implementation too much, since we might add more to the language in the future.
Here is the result:
I'm also fixing the storage benchmark that is currently crashing because of a change in the limits.