[cfarm-users] Does cfarm421 need more RAM?

[Martin Guy]

Il 27/03/24 08:48, Pierre Muller via cfarm-users ha scritto:

> I'm the maintainer of cfarm{420,421,422} and I noticed that cfarm421
>> spits out these in the kernel log message buffer:
>>
>> ================8<=============8<===============
>> [407044.868840] __vm_enough_memory: pid: 1547477, comm: qemu-aarch64,
>> not enough memory for the allocation
>> [407044.873072] __vm_enough_memory: pid: 1547477, comm: qemu-aarch64,
>> not enough memory for the allocation
>> [407793.227963] __vm_enough_memory: pid: 1629843, comm: qemu-loongarch6,
>> not enough memory for the allocation
>> [407793.252490] __vm_enough_memory: pid: 1629843, comm: qemu-loongarch6,
>> not enough memory for the allocation
>> [408951.450373] __vm_enough_memory: pid: 1782006, comm: qemu-ppc64, not
>> enough memory for the allocation
>> [408951.455591] __vm_enough_memory: pid: 1782006, comm: qemu-ppc64, not
>> enough memory for the allocation
>> [409186.357363] __vm_enough_memory: pid: 1813298, comm: qemu-ppc64le,
>> not enough memory for the allocation
>> [409186.361280] __vm_enough_memory: pid: 1813298, comm: qemu-ppc64le,
>> not enough memory for the allocation
>> [409864.075096] __vm_enough_memory: pid: 1873876, comm: qemu-riscv64,
>> not enough memory for the allocation
>> [409864.084699] __vm_enough_memory: pid: 1873876, comm: qemu-riscv64,
>> not enough memory for the allocation
>> [410768.150482] __vm_enough_memory: pid: 1934927, comm: qemu-sparc64,
>> not enough memory for the allocation
>> [410768.156067] __vm_enough_memory: pid: 1934927, comm: qemu-sparc64,
>> not enough memory for the allocation
>> [411410.679436] __vm_enough_memory: pid: 1964674, comm: qemu-x86_64, not
>> enough memory for the allocation
>> [411410.684506] __vm_enough_memory: pid: 1964674, comm: qemu-x86_64, not
>> enough memory for the allocation
>> [430615.068394] __vm_enough_memory: pid: 2110282, comm: qemu-aarch64,
>> not enough memory for the allocation
>> [430615.083721] __vm_enough_memory: pid: 2110282, comm: qemu-aarch64,
>> not enough memory for the allocation
>> [433503.627242] __vm_enough_memory: pid: 2347231, comm: qemu-ppc64, not
>> enough memory for the allocation
>> [433503.631411] __vm_enough_memory: pid: 2347231, comm: qemu-ppc64, not
>> enough memory for the allocation
>> [433935.278186] __vm_enough_memory: pid: 2383232, comm: qemu-ppc64le,
>> not enough memory for the allocation
>> [433935.283613] __vm_enough_memory: pid: 2383232, comm: qemu-ppc64le,
>> not enough memory for the allocation
>> [435267.994912] __vm_enough_memory: pid: 2456518, comm: qemu-sparc64,
>> not enough memory for the allocation
>> [435268.002203] __vm_enough_memory: pid: 2456518, comm: qemu-sparc64,
>> not enough memory for the allocation
>> [436006.040243] __vm_enough_memory: pid: 2491131, comm: qemu-x86_64, not
>> enough memory for the allocation
>> [436006.061130] __vm_enough_memory: pid: 2491131, comm: qemu-x86_64, not
>> enough memory for the allocation
>> [449685.944334] __vm_enough_memory: pid: 3055522, comm: tw2494, not
>> enough memory for the allocation
>> [449685.948704] __vm_enough_memory: pid: 3055522, comm: tw2494, not
>> enough memory for the allocation
>> [450558.392384] __vm_enough_memory: pid: 3091900, comm: tw2494, not
>> enough memory for the allocation
>> [450558.396205] __vm_enough_memory: pid: 3091900, comm: tw2494, not
>> enough memory for the allocation
>> ================8<=============8<===============
>> root at cfarm421:~# free -h
>>                  total        used        free      shared buff/cache
>> available
>> Mem:            64Gi       4.5Gi        20Gi       1.6Mi 40Gi
>>      60Gi
>> Swap:             0B          0B          0B
>> ================8<=============8<===============
>
>   Test tw2494 is specifically a test that checks what is happening
> if the program tries to allocate 4096 Tb (=2Gb*2Gb).


I was going to say "Give it some swap space?" but that seems so obvious 
to be fatuous, however, I wonder if the system running out of VM might 
affect other processes on the same machine.

Pierre, can you obtain the same effect by using ulimit?


     M

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 665 bytes
Desc: OpenPGP digital signature
URL: <http://lists.tetaneutral.net/pipermail/cfarm-users/attachments/20240327/c96d6c36/attachment-0001.sig>