[SERVER-70711] Improve performance of venv setup Created: 19/Oct/22 Updated: 02/Feb/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alex Neben | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Build
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently it takes ~40 seconds to set up the venv. Maybe there is something we can do to improve this. Worth taking a look at because this has to be done before testing starts on evergreen. |
| Comments |
| Comment by Ryan Egesdahl (Inactive) [ 01/Nov/22 ] |
|
One way I can think of to solve this problem is to move the venv build process to an external mechanism, such as a different project that only builds the venv and uploads it for other projects to use. The main benefit of this approach apart from moving the venv build out of the critical chain is that we will have the opportunity to eventually remove much of the version pinning in our venv because we can always use the "last known good" venv. However, this would also be a more time-intensive approach, so it might be a bit much spend for a 40 second performance gain. Perhaps there's a piece we can take from this idea that solves the immediate problem? |
| Comment by Alex Neben [ 19/Oct/22 ] |
|
This also gets run again as part of version_expansions_gen. So this is run 2x. |