# Memory Requirements for compiling Mender 4.X through Yocto **URL:** \ **Category:** General Discussions\ **Tags:** yocto, mender-client\ **Created:** [March 15, 2024, 12:04pm UTC](https://hub.mender.io/t/memory-requirements-for-compiling-mender-4-x-through-yocto/6632 "2024-03-15T12:04:25Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![pyxlwuff](https://avatars.discourse-cdn.com/v4/letter/p/898d66/32.png) [@pyxlwuff](https://hub.mender.io/u/pyxlwuff)\ **Post date:** [March 15, 2024, 12:04pm UTC](https://hub.mender.io/t/memory-requirements-for-compiling-mender-4-x-through-yocto/6632/1 "2024-03-15T12:04:25Z")
Hi there, I’ve noticed that when trying to compile the 4.0 client through Yocto, memory usage seems to have doubled, and my build system ends up completely killing everything because it runs out of memory. Is this an intentional change? Going from 7gb of memory usage to the entire 16 + swap once it starts trying to compile the mender client doesn’t seem right. It’s an 8 core machine (i7 11700) with 16gb of RAM at the moment. ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [March 15, 2024, 7:54pm UTC](https://hub.mender.io/t/memory-requirements-for-compiling-mender-4-x-through-yocto/6632/2 "2024-03-15T19:54:44Z")
Hi @pyxlwuff, It’s definitely not “intentional”. A first guess would be that boost compilation runs into OOM, as that is a new dependency. Do you have any pointers on which compilation stage actually gets aborted? Greets, Josef ---
**Author:** ![pyxlwuff](https://avatars.discourse-cdn.com/v4/letter/p/898d66/32.png) [@pyxlwuff](https://hub.mender.io/u/pyxlwuff)\ **Post date:** [March 15, 2024, 8:21pm UTC](https://hub.mender.io/t/memory-requirements-for-compiling-mender-4-x-through-yocto/6632/3 "2024-03-15T20:21:18Z")
Hi Josef, It gets aborted on the do\_compile stage of mender 4.0.1. I’ve also ran bitbake with BB\_NUMBER\_THREADS=1 and it always will completely lock up when it gets to the client. Weirdly this doesn’t happen if I were to compile the client myself, only through Yocto ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [March 19, 2024, 11:14am UTC](https://hub.mender.io/t/memory-requirements-for-compiling-mender-4-x-through-yocto/6632/4 "2024-03-19T11:14:27Z")
Hi @pyxlwuff, Sorry for taking some time. This definitely should not happen. One possible thing to look into the the `PARALLEL_MAKE` variable. Can you maybe inspect it for the `mender` 4.0.1 recipe? Greets, Josef ---
**Author:** ![pyxlwuff](https://avatars.discourse-cdn.com/v4/letter/p/898d66/32.png) [@pyxlwuff](https://hub.mender.io/u/pyxlwuff)\ **Post date:** [March 19, 2024, 12:13pm UTC](https://hub.mender.io/t/memory-requirements-for-compiling-mender-4-x-through-yocto/6632/5 "2024-03-19T12:13:41Z")
Hi Josef, I experimented by adding `PARALLEL_MAKE` to the recipe and got the following results: Set to 4 it froze around 36% before completely freezing at 42% Set to 2 it froze immediately Set to 1 it froze, then was killed by the memory manager. This was all with `BB_NUMBER_THREADS=1 bitbake ` ---
**Author:** ![pyxlwuff](https://avatars.discourse-cdn.com/v4/letter/p/898d66/32.png) [@pyxlwuff](https://hub.mender.io/u/pyxlwuff)\ **Post date:** [March 19, 2024, 1:52pm UTC](https://hub.mender.io/t/memory-requirements-for-compiling-mender-4-x-through-yocto/6632/6 "2024-03-19T13:52:30Z")
After giving myself a ridiculously sized swapfile (around 16GB), I was able to get Mender 4.0.1 to compile successfully through Yocto. With `htop` open in another terminal window, I saw it seems to spawn around 10-12 processes when compiling. At its peak it was using \>22GB of memory for do\_compile across RAM and Swap. I’m not too sure if this is to do with the cmake bbclass that’s being used, or if its something else entirely, but it doesn’t seem like it’s respecting `PARALLEL_MAKE`.