On Sun, Oct 03, 2021 at 10:21:16AM -0400, Reinhard Tartler wrote: >... > The consistent OOM is surprising given that you state that the worker has > 250GB of RAM. Looking at the logs, > I note that the tests are being passed the option -p 160 by the dh-golang > helper, so it will build > and run test executables concurrently. That confirms to me that we are > indeed running on these 250GB/160 core workers. >...
No matter the amount of RAM, you will always have the limitation of <= 4 GB address space for a process on 32bit.[1] Starting one process per core is not a problem even if each process uses takes 1 GB of RAM.[2] Starting one thread per core in the same process would not be suprising to fail, 20 MB per thread would suffice for running out of address space. > regards, > Reinhard cu Adrian [1] 32bit arm has 3 GB address space [2] 160 g++ processes might be a problem with only 1.5 GB RAM per core
