[SERVER-11290] Don't put linked products in build cache Created: 21/Oct/13 Updated: 06/Dec/22 Resolved: 21/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Build Team (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | build-needs-definition, build-planning | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Build
|
||||||||
| Participants: | |||||||||
| Description |
|
Putting the executables and libraries in the cache causes severe write amplification for little if any gain. I think only .o files (and equivalents) belong in the cache. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 21/Mar/17 ] |
|
This work was actually done as part of |
| Comment by Githook User [ 14/Jul/14 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: We don't currently use the static libraries, they are just nodes in our We still need to generate the files to appease scons. They are filled with a |
| Comment by Andy Schwerin [ 23/Oct/13 ] |
|
Given our current build approach of linking .o files directly into binaries and shared libraries, we could replace static libraries on all platforms with files full of (obj file name, MD5 hash) pairs, and get the same effect with substantial space savings. |