On Wed, Jan 27, 2021 at 2:43 PM Boris Ranto <branto@xxxxxxxxxx> wrote: > We are constantly running into this issue. The mem_per_process does help but it is just a heuristic and needs to be tuned quite frequently. > > The last time this occurred, I did give it some thought. What if we tuned the build system a little? We could identify the biggest memory hogs and build them sequentially (post-parallel build?). I know ceph-dencoder was super-memory-expensive (it required more than 4G of RAM even on 32-bit architectures so we couldn't even build on 32-bit architectures anymore) and it might be a first candidate on the 'sequential' list. Do we have any other culprits? > > What do you think? I think this is a great idea. How do we do this in CMake? - Ken _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
