Building the server sources is fairly resource intensive. I recommend using the most powerful machine you can. But there are a few things you can try to reduce various sorts of resource constraints:
-
By default the build will use all available cores as found by the python
psutillibrary. But you can reduce that on the command line by passing an explicit-j Nargument. Cutting thatNvalue back from using all your local cores should reduce the memory pressure during compilation. -
Linking a static
mongodbinary can take a lot of memory. If you don’t need a production quality binary, you can build with--link-model=dynamic, which will instead build amongodthat links tons of little shared libraries. That makes the final link much less resource intensive. -
If you must go with a static build but don’t need debug info after development, you can try building with
CCFLAGS=-gsplit-dwarf, which should reduce the amount of memory and disk used to manage debug info, but the resulting build is really only appropriate for development use since you can’t take the debug info with you easily. Note that you are already passing an argument toCCFLAGS, so the syntax for passing multiple values is a space separated string:scons ... CCFLAGS="-march=core2 -gsplit-dwarf". There isn’t much use to-gsplit-dwarffor a--link-model=dynamicbuild, in our experience. -
You can save a disk space on the installation by building with
--install-action=hardlink, which will hardlink files into the installation directory, rather than copying them from the build directory. This will only work as long as your build directory and installation directory are on the same filesystem. If you have customizedDESTDIRor similar, that may not be true.
All of the above comes with the caveat that all our developer experience with these flags is from macOS and Linux. So, just like with the code itself, your mileage may vary on BSDs.
Andrew