[SERVER-74279] reevaluate link job caching for evergreen Created: 22/Feb/23 Updated: 27/Oct/23 Resolved: 27/Oct/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 |
|
Potentially there is a optimization for caching dynamic link binaries, the time to link is generally 1-5 seconds and the time to transfer from cache is about a 1-2 seconds. The downside to consider is that almost any code change will induce many dynamic link bins to be recached, due to the nature of the dynamic link bins begin far down the dependency tree.
In |
| Comments |
| Comment by Daniel Moody [ 23/Feb/23 ] |
|
I looked at some data, and for shared libs, a transfer is on the order 10s of milliseconds while a relink of is on the order of 100s of milliseconds. I think we should continue to not cache shared libs due to number of files and size implications for shared libs in the cache. |