Hacker News Reader

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?

View on HN

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.

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).

Doesn't blaze build remotely via citc? I thought files were loaded locally for editing but built remotely.

Blaze itself runs locally, reading BUILD files from citc. The build actions mostly execute remotely.

Reply on news.ycombinator.com