memory and swap on the buildds
noticed that we have different (and somehow low) memory and swap configurations on the buildds
amd64, i386: 8G RAM, 4G swap
arm64, armhf, ppc64el: 8G RAM, no swap
s390x: 16G RAM, no swap
I'm currently not able to build a GCC with pgo and lto optimizations enabled, also we had some build failures in the hirsute cycle which might be OOM killers (no build log, so we don't know for sure).
Please could we configure the buildds in a way that they have 16G of space (8G RAM, 8G swap)? Looking at the Debian buildds, these are usually configured with a lot more of swap space, some of them having 8G RAM as well.
Question information
- Language:
- English Edit question
- Status:
- Open
- Assignee:
- Colin Watson Edit question
- Last query:
- Last reply:
| Matthias Klose (doko) said : | #1 |
riscv64: 16G RAM, no swap
| Launchpad Janitor (janitor) said : | #2 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.
| Matthias Klose (doko) said : | #3 |
re-opening
| Colin Watson (cjwatson) said : | #4 |
Your findings about s390x don't agree with what I found when I went looking: https:/
The arm64/armhf/ppc64el behaviour is interesting. The configured nova flavour is correct, but inspecting the situation on a staging builder, it looks as though cloud-init is being told that the root and swap disks are the wrong way round (/dev/vda and /dev/vdb respectively, when they actually appear to be the other way round). Fixing that is going to require some digging - I suspect OpenStack is configured slightly wrongly, but I'm not sure exactly how.
Once we get this fixed, changing the vbuilder flavour on each region to specify 8G swap should be easy enough.
| Colin Watson (cjwatson) said : | #5 |
I've filed https:/
Can you help with this problem?
Provide an answer of your own, or ask Matthias Klose for more information if necessary.
