[SERVER-79481] Define an upper bound for the number of multiple open buckets per metadata Created: 28/Jul/23 Updated: 31/Jan/24 Resolved: 31/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Damian Wasilewicz |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution Team 2024-02-05 | ||||
| Participants: | |||||
| Linked BF Score: | 36 | ||||
| Description |
|
We'll need this to avoid opening too many buckets for the same metadata. We can start with 5 for now and tune it during performance testing. We will likely see buckets getting filled slower as a consequence of this approach. It will be essential to ensure finalized buckets remain full so as not to impact query performance by loading more and smaller buckets. |
| Comments |
| Comment by Githook User [ 31/Jan/24 ] |
|
Author: {'name': 'Damian Wasilewicz', 'email': '33820523+DamianWasilewicz@users.noreply.github.com', 'username': 'DamianWasilewicz'}Message: GitOrigin-RevId: de7a746bd8ab4a27169b640204b9696402331668 |