Re: To Tomas Vondra > It's the very same kernel, just different docker containers on the > same system. I did not investigate yet where the problem is coming > from, different libnuma versions seemed like the best bet.
numactl shows the problem already: Host system: $ numactl --show policy: default preferred node: current physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 cpubind: 0 nodebind: 0 membind: 0 preferred: debian:trixie-slim container: $ numactl --show physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 No NUMA support available on this system. debian:bookworm-slim container: $ numactl --show get_mempolicy: Operation not permitted get_mempolicy: Operation not permitted get_mempolicy: Operation not permitted get_mempolicy: Operation not permitted policy: default preferred node: current physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 cpubind: 0 nodebind: 0 membind: 0 preferred: Running with sudo does not change the result. So maybe all that's needed is a get_mempolicy() call in pg_numa_available() ? Christoph
