зеркало из https://github.com/microsoft/BuildXL.git
76adb87e41
Currently it only remotes process pip with "compile" tag. The remoting configuration is still not optimal currently, particularly for the beefy pool we have (32 cores). In this run, https://dev.azure.com/mseng/Domino/_build/results?buildId=16779538&view=results, with remoting multiplier 1.5, and num of leases is assumed to be 2*maxproc, there are 42 processes going to AnyBuild, but 22 of them failed to find agents because AnyBuild is over saturated. In this run, https://dev.azure.com/mseng/Domino/_build/results?buildId=16779745&view=results, with remoting multiplier 1.25 and num of leases 24, there are only 17 processes going to AnyBuild, and all of them successfully execute remotely. More work is still needed for optimal configuration, e.g., - Feedback from AnyBuild about available leases, etc. Related work items: #1912875 |
||
|---|---|---|
| .. | ||
| az-login.yml | ||
| install-client.yml | ||
| pipeline.yml | ||
| validate.yml | ||