-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Document rough guidelines on sizing store gateway #4802
Comments
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Despite it being more than two weeks it looks like this is still open. I still think there's a benefit to a scaling document. It'd be nice to understand when we should shard or memory settings. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Bumping this. I still think some general guidance on how to size things would be helpful. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Bump, I'd also find this useful! |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Remove stale |
I also find this important to have as Thanos store have different flags and configuration scenarios we can rely on to have a reliable deployment |
Is your proposal related to a problem?
I'm getting OOMs on my storegateways when trying to make queries of a certain size in grafana. I'm not looking for some magical switch to make it start working but some docs on how to tune the store gateways and which variables should be taken into consideration when doing that sizing. For example, I see this comment #1750 (comment) which starts to list how many objects in the store and total size of bucket. Are there other factors to look at there?
Additionally it'd be great to know when to consider sharding and performance impacts of choosing in-memory vs memcached for caching.
Describe the solution you'd like
See above
Describe alternatives you've considered
I've tried to find other examples but don't find much that discusses scale AFAIK.
Additional context
The text was updated successfully, but these errors were encountered: