[SERVER-74322] consider removing thin archive caching Created: 23/Feb/23 Updated: 23/Feb/23 Resolved: 23/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Moody | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Participants: |
| Description |
|
We should look at the time difference between caching and transferring the thin_archives vs just rebuilding them each time.
even though we switched away from caching linked bins in https://jira.mongodb.org/browse/SERVER-74278, thin archives are still cached: https://jira.mongodb.org/browse/SERVER-33958 |
| Comments |
| Comment by Daniel Moody [ 23/Feb/23 ] |
|
I looked into it, and a transfer time is on the order of 10s of milliseconds vs 1-2 seconds to rebuild locally. There is around 1000 libs so after dividing by the j for a rough estimate of total time delay for the build its on the order of 10s of seconds. I think we should maintain caching the thin_archives so I will close this ticket as wont do. |