diff options
author | Ross Burton <ross@burtonini.com> | 2021-11-24 17:15:29 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-11-25 21:55:10 +0000 |
commit | c6f23f1f0fad29da4dee27a9cb8219ae05a8bfd5 (patch) | |
tree | 287aa74517c481c4b2f0b257a4a3a916a7758450 /meta-skeleton/recipes-core | |
parent | 317511ce1fa8bf2270fa86798dc53353e6335087 (diff) | |
download | poky-c6f23f1f0fad29da4dee27a9cb8219ae05a8bfd5.tar.gz |
oe/utils: by default cap cpu_count() to 64 cores
Larger systems may have large numbers of cores, but beyond a certain
point they can't all be used for compiling: whilst purely
compute-intensive jobs can be parallelised to hundreds of cores,
operations such as compressing (needs lots of RAM) or compiling (lots of
I/O) don't scale linearly.
For example, the Marvel ThunderX2 has 32 cores, each capable of
executing four threads, and can be configured with two sockets, making
256 CPUs according to Linux. Zstd using 256 threads has been seen to
fail to allocate memory during even small recipes such as iso-codes.
Add a default cap of 64 CPUs to the cpu_count() method so that extreme
parallisation is limited. 64 is high enough that meaningful gains
beyond it are unlikely, but high enough that most systems won't be
effected.
(From OE-Core rev: 765d0f25ce48636b1838a5968e2dc15de2127428)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-skeleton/recipes-core')
0 files changed, 0 insertions, 0 deletions