Overview
Request 710105 accepted
- Take SwapTotal into account, MemTotal only reflects physical memory. Some
workers have a considerable amount of swap.
- Created by StefanBruens
- In state accepted
Loading...
Request History
StefanBruens created request
- Take SwapTotal into account, MemTotal only reflects physical memory. Some
workers have a considerable amount of swap.
scarabeus_iv accepted request
ok lets try it, if it breaks up we will revert it back.
we didn't account for swap on purpose, it is too slow
I have tested this with qt5-qtwebengine, and it is a significant win there. E.g. some (all?) worker instances on morla* have 8+4 GB of mem and SMP 6. Withouth swap, the build is limited to 4 jobs, with swap it uses 6 jobs.
The higher the job count, the less likely it becomes you hit the peak memory of jobs * mem_per_job. Most of the time, the running jobs will run fine with just the physical memory.
Thx!
Maybe the problem is in fact that the
-margument is too small? I had a similar issue in llvm and as it turns out the compile jobs didn't really need 1500 MB. (It was also arch-dependent, on 32-bit platforms memory usage was usually lower.)Usually you only want to use a little bit of swap to work around memory peaks. If you use all of it, you will not see the build job finish. So the total amount of swap is pretty irrelevant.