phlax

in a local setup jobs=num of cpus in remote jobs=num of workers (irrespective of their core count) > I am still new to bazel so its good that I am...

> many gigabytes of RAM do you have? It might be the case that your builds generally succeed 32GB and 16 cores - i think bazel can take 3-4G per...

im not sure its the right solution for the right problem rn - it uses all cpus-1 - not sure this would actually change that - it would just prevent...

> ...so let's set the CPUs to what the system can handle while still being able to build. the problem is that nearly all the jobs take very little memory...

thanks @leonematt ! that would be really appreciated

i should also mention - we recently landed a PR to optimize foreign_cc builds (ie c/make etc non-bazel builds) the optimization is to use all cores - which in some...

> Yeah, the local build system does this by default. im not 100% clear about this (either way) - from my limited testing at least with cmake jobs i had...

thinking through current impl - im remembering why i did it this way - ie 1 or all ... in the rbe/ci context we want all - similar for local...

afaict feedback still needs to be addressed /wait-any

@asedeno this (re-) adds a bit of noise to the build ```console external/com_google_cel_cpp/common/internal/reference_count.cc:83:33: warning: offset of on non-standard-layout type 'cel::common_internal::(anonymous namespace)::ReferenceCountedString' [-Winvalid-offsetof] internal::SizedDelete(that, offsetof(ReferenceCountedString, data_) + size); ^ ~~~~~ /opt/llvm/lib/clang/14.0.0/include/stddef.h:104:24:...