-
Notifications
You must be signed in to change notification settings - Fork 816
Larger buckets in chunk index #10
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
Comments
From @jml @tomwilkie Do you have some idea for how much larger they should be, or thoughts on how to determine how much larger? |
From @tomwilkie Chunk index 'big' bucket size mainly affects the number of range queries you need to do on query. Smaller buckets = more range queries = more dynamodb cost & slower queries. OTOH larger buckets mean more chunks / bucket, which means more items returned in the range queries. Limit on dynamodb range queries is 25 items before you start paging. So we should look and see how many chunks / query we are getting, and tune that until it hits 25. I have a feeling it will be 24hrs... |
We need to gather stats on pages per query before deciding on this, but its looks like we are going toward bigger chunks, so 24hr buckets might be a good idea. |
Code is in, flag just needs deploying to dev and testing. |
Has been deployed to prod and will go live tomorrow. |
Cortex Release
From @tomwilkie
Should reduce index size, super important for scalability.
Copied from original issue: tomwilkie/frankenstein#9
The text was updated successfully, but these errors were encountered: