Showing 1 post
Bazel’s original raison d’etre was to support Google’s monorepo. A consequence of using a monorepo is that some builds will become very large. And large builds can be very resource hungry, especially when using a tool like Bazel that tries to parallelize as many actions as possible for efficiency reasons. There are many resource types in a system, but today I’d like to focus on the number of open files at any given time (nofiles
).
January 29, 2019
·
Tags:
bazel, jvm, macos, monorepo, portability
Continue reading (about
3 minutes)