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

feat: configure Thanos caching #64

Merged
merged 4 commits into from
Feb 7, 2024
Merged

feat: configure Thanos caching #64

merged 4 commits into from
Feb 7, 2024

Conversation

modridi
Copy link
Contributor

@modridi modridi commented Nov 30, 2023

Description of the changes

A frontend response cache of 2 hours is configured for better subsequent query processing.
A store gateway metrics index cache is also configured to enhance bucket stored metrics lookup operations.

Breaking change

  • No
  • Yes (in the Helm chart(s)): indicate the chart, version & release note link
  • Yes (in the module itself): give an explanation of the breaking change

Tests executed on which distribution(s)

  • KinD
  • AKS (Azure)
  • EKS (AWS)
  • Scaleway
  • SKS (Exoscale)

@modridi modridi force-pushed the thanos-perf-tuning branch 5 times, most recently from 78d72fd to e13a7ff Compare December 6, 2023 08:32
@modridi modridi marked this pull request as ready for review December 6, 2023 09:24
@modridi modridi requested a review from a team as a code owner December 6, 2023 09:24
@modridi modridi changed the title feat: configure query spitting & cache feat: configure query splitting & cache Dec 6, 2023
@modridi modridi changed the title feat: configure query splitting & cache feat: configure Thanos caching Dec 22, 2023
@modridi modridi merged commit 131e6e4 into main Feb 7, 2024
@modridi modridi deleted the thanos-perf-tuning branch February 7, 2024 14:06
@github-actions github-actions bot mentioned this pull request Feb 7, 2024
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

Successfully merging this pull request may close these issues.

2 participants