[SERVER-61380] audit jlink values after v4 toolchain is required Created: 10/Nov/21 Updated: 08/Jan/23 Resolved: 27/Dec/22 |
|
| 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: | Alex Neben |
| Resolution: | Done | Votes: | 0 |
| Labels: | post-v4-toolchain | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
Over time we have been reducing the jlink values for many builders due to memory limts. We should investigate if the v4 toolchain has added optimization to reduce memory footprints and if we can increase any of these values. |
| Comments |
| Comment by Alex Neben [ 27/Dec/22 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Doing only the link for mongod in v6.0 we get a `Maximum resident set size (kbytes): 10049664` Since the memory usage increases we cannot increase the jlink value. | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Alex Neben [ 27/Dec/22 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Looks like there was a 50% difference so I am going to zoom in on a specific link
| ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Alex Neben [ 14/Dec/22 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
I think this would be good to check out in a timebox but my guess is that the memory footprint won't change much. |