[SERVER-66738] Evaluate options for improving performance with large time-series measurements Created: 24/May/22 Updated: 29/Oct/23 Resolved: 16/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution Team 2022-06-13, Execution Team 2022-06-27 | ||||
| Participants: | |||||
| Description |
|
Currently if we have large measurements, we can end up keeping relatively few measurements per bucket. We may wish to increase the default value of the timeseriesBucketMaxSize parameter. Alternatively, we may wish to only consider closing the bucket due to size if we have a certain minimum number of measurements (e.g. 5) or if it would cause the bucket to violate the object size limit (16MiB). |
| Comments |
| Comment by Githook User [ 16/Jun/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |