Implement `--experimental_memory_load_scheduling` in Bazel. Add experimental local execution action scheduling based on host memory utilization to `ResourceManager` and `MachineLoadProvider`, addressing issue #10662 for memory load scheduling. - Extend `MachineLoadProvider` with `getCurrentMemoryUsageMb()` to measure live RAM usage via `ProcMeminfoParser` (on Linux) or `OperatingSystemMXBean`. - Add `--experimental_memory_load_scheduling` flag in `ExecutionOptions`. - Update `ResourceManager` to dynamically check live host memory usage plus window estimation (`windowEstimationMemory`) when scheduling local actions in `areResourcesAvailable()`. - Rename `scheduleCpuLoadWindowUpdate()` to `scheduleLoadWindowUpdate()` to reflect scheduling for both CPU and memory load. - Remove deprecated `scheduleCpuLoadWindowUpdate()` and `initializeCpuLoadFunctionality()` wrappers. - Add unit tests in `ResourceManagerTest`. - Add `test_experimental_load_scheduling` shell integration test in `bazel_localtest_test.sh` testing `--experimental_memory_load_scheduling` and `--experimental_cpu_load_scheduling`. PiperOrigin-RevId: 969832855 Change-Id: I539e3de73307857cd8197e3e4c14f078e1ed79b0
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
