dbbcb47695
This is the first phase of giving more love to cache miss analysis: improving the analysis presentation.
The current presentation has the following issues:
- Analysis outputs are hard to understand, and look cryptic.
- Cache miss analysis relies on a buggy third-party algorithm that can spit out a lot of irrelevant outputs.
- Analysis of weak fingerprint do not respect order-independent entries.
- Etc.
The new presentation is still Json based and is similar to (but more refined than) the legacy cache miss analysis (which customers like).
Example of new presentation (for mismatched strong fingerprints):
```
{
"StrongFingerprint": {
"Old": "471383773F3C19EAC1F4EF4DDD496E2076428406",
"New": "FA15D762D7BFE52570BDFC070917B4103E0EE713"
},
"Paths": {
"Changed": {
"b:\\out\\objects\\7\\0\\907noclwl174l942adk4eeeedjrh2a\\t_1\\fingerprints73945ac\\0\\obj\\readonly\\src_0": {
"Old": "AccessType: DirectoryEnumeration | Hash: 3100D2E3F4",
"New": "AccessType: DirectoryEnumeration | Hash: C675A28412",
"Members": {
"Added": [
"src_3",
"src_4"
]
}
}
}
}
}
```
The old presentation is preserved because some customer (namely Eric) relies on the old format.
Related work items: #1520132, #1567602, #1572558
|
||
|---|---|---|
| .vscode | ||
| Documentation | ||
| Examples | ||
| Private | ||
| Public | ||
| Shared | ||
| cg | ||
| third_party | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| BuildCache.cmd | ||
| BuildCacheDefault.json | ||
| BuildCacheDefaultNetCore.json | ||
| BuildCacheOverride.json | ||
| CODEOWNERS | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| CreatePr.cmd | ||
| LICENSE | ||
| README.md | ||
| RunCheckInTests-Test.cmd | ||
| RunCheckInTests.cmd | ||
| RunCheckInTestsWithPAT.ps1 | ||
| SECURITY.md | ||
| SlimBuildForMacTests.cmd | ||
| buddy.cmd | ||
| bxl.cmd | ||
| bxl.sh | ||
| clean.bat | ||
| config.dsc | ||
| config.microsoftInternal.dsc | ||
| config.nuget.aspNetCore.dsc | ||
| config.nuget.vssdk.dsc | ||
| domino.cmd | ||
| drop.cmd | ||
| dropout.cmd | ||
| macos.mounts.dsc | ||
README.md
Microsoft Build Accelerator
Introduction
Build Accelerator, BuildXL for short, is a build engine originally developed for large internal teams at Microsoft, and owned by the Tools for Software Engineers team, part of the Microsoft One Engineering System internal engineering group. Internally at Microsoft, BuildXL runs 30,000+ builds per day on monorepo codebases up to a half-terabyte in size with a half-million process executions per build, using distribution to thousands of data center machines and petabytes of source code, package, and build output caching. Thousands of developers use BuildXL on their desktops for faster builds even on mega-sized codebases.
BuildXL accelerates multiple build languages, including:
- MSBuild (using new features under development in MSBuild 16 which will ship in future versions of Visual Studio 2019 and the .NET Core SDK)
- CMake (under development)
- Its own internal scripting language, DScript, an experimental TypeScript based format used as an intermediate language by a small number of teams inside Microsoft
BuildXL has a command-line interface. There are currently no plans to integrate it into Visual Studio. The project is open source in the spirit of transparency of our engineering system. You may find our technology useful if you face similar issues of scale. Note that BuildXL is not intended as a replacement for MSBuild or to indicate any future direction of build languages from Microsoft.
Documentation
The BuildXL documentation main page is here.
Examples and Demos
See the Examples/ folder for basic project examples. See the Demos page for information about various technical demos like using the process sandboxing code.
Building the Code
Build Status - Azure DevOps Pipelines
Command Line Build and Test
See the Developer Guide for instructions on compiling BuildXL.
Contributing
See CONTRIBUTING.