-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2024-12-23, CAR Team 2025-01-06
-
2
Our remote compilation environment is limited to 3.5GB of ram per compilation by default. With SERVER-97735, it is pushed over that limit and gets killed. It is possible that even without that change it was getting close to the limit and possibly swapping out the compiler leading to much slower compiles that it should have. Therefore it was moved to the "high memory" pool which is twice as expensive. Either:
- Try to split up that cpp file into smaller files that are cheaper to compile. This should also speed up compilation by making it more parallelizable and having less to rebuild when editing the smaller cpp. If you do this, remove the exec_properties block in the BUILD.bazel file.
- Pull that cpp file out to its own library, and move the exec_properties to the new library. While it won't reduce the resources used to compile it, it will avoid using the more expensive instances to compile the other files in its library.
- is related to
-
SERVER-97735 Support debug-fission/split-dwarf with bazel
- Closed