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.

Sign up for GitHub

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

Jump to bottom

Tune chunk size #10

Closed
tomwilkie opened this issue Aug 30, 2016 · 3 comments
Closed

Tune chunk size #10

tomwilkie opened this issue Aug 30, 2016 · 3 comments
Milestone
SF Prometheus Meetup

Comments

@tomwilkie
Copy link
Owner

Currently 10mins, should be 1hr.
@jml
Copy link
Collaborator

jml commented Sep 6, 2016

Why should it be 1hr?

@tomwilkie
Copy link
Owner Author

We should investigate what the right number is, but the parameters are:

  • data batched up in the ingesters is a risk of loss in event of machine failure. we should bound this.
  • chunks are 1kb, and making bigger chunks doesn't necessarily make things more efficient. we should try and fill chunks as much as possible (something we already monitoring for).

Ticket should really say "max 1hr" to bound the loss, if that give good utilization

@jml jml mentioned this issue Sep 9, 2016
Closed
@jml
Copy link
Collaborator

jml commented Sep 9, 2016

This issue was moved to cortexproject/cortex#11

@jml jml closed this as completed Sep 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
SF Prometheus Meetup
Development

No branches or pull requests
2 participants
@jml @tomwilkie