Launchpad itself

memory and swap on the buildds

Asked by Matthias Klose

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:
Answered
For:
Launchpad itself Edit question
Assignee:
Colin Watson Edit question
Last query:
Last reply:
Revision history for this message
Matthias Klose (doko) said : 		#1

riscv64: 16G RAM, no swap

Revision history for this message
Launchpad Janitor (janitor) said : 		#2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Matthias Klose (doko) said : 		#3

re-opening

Revision history for this message
Colin Watson (cjwatson) said : 		#4

Your findings about s390x don't agree with what I found when I went looking: https://launchpadlibrarian.net/527421412/buildlog_ubuntu-hirsute-s390x.procenv_0.51-0.2_BUILDING.txt.gz shows "SwapTotal: 4194300 kB". So that's at least consistent with what the current configuration is supposed to be on all architectures.

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.

Revision history for this message
Colin Watson (cjwatson) said : 		#5

I've filed https://portal.admin.canonical.com/C130104 for the missing-swap part of this.

Revision history for this message
Nicholas Guriev (mymedia) said : 		#6

I discovered amd64 builders lost their 4GB swap and have only 8GB RAM left. What is not enough for LTO of large packages.

Revision history for this message
Colin Watson (cjwatson) said : 		#7

@mymedia Thanks for bringing this up. That's a different problem from the arm64/armhf/ppc64el situation: in this case, the relevant OpenStack flavour on lcy02 is just incorrectly configured, lacking swap. I've filed https://portal.admin.canonical.com/C149050 internally for that.

Revision history for this message
Colin Watson (cjwatson) said : 		#8

While the arm64/armhf/ppc64el swap situation is still open, all builders now have 16 GB of RAM, which fulfils the original request.

Can you help with this problem?

Provide an answer of your own, or ask Matthias Klose for more information if necessary.

To post a message you must log in.