Re:Bazel Build System Support for LLVM
by jsolson on Thursday October 29, 2020 @02:09AM
(#24927764)
I'm curious what you consider "insane" to be -- and I mean this genuinely. Google has what I think most would consider to be a large monorepo, but also provides developer desktops with ample RAM. I've noticed blaze's startup time, but never really thought about its memory consumption. Where are you running into limits?
[ Parent
| on HN ]
Re:Bazel Build System Support for LLVM
by an_d_rew on Wednesday November 04, 2020 @05:33PM
(#24993745)
10,000+ artifacts on a 20 core Intel box with 64 Gb RAM.
We have some peculiarities of our Bazel setup that are not common, yet are (supposed to be) fully supported.
Building can take hours.
Re:Bazel Build System Support for LLVM
by laurentlb on Thursday November 05, 2020 @08:27AM
(#24998010)
Are you using remote execution with Bazel?
If you have hour long builds, it's often worth investing in remote execution (just remote caching can help too).
Re:Bazel Build System Support for LLVM
by smiths1999 on Thursday October 29, 2020 @06:13AM
(#24928861)
Doesn't blaze build remotely via citc? I thought files were loaded locally for editing but built remotely.