adoptium
Replace AWS Linux/aarch64 perf machines with OSUOSL ones
I need to request a new machine:
- New machine operating system (e.g. linux/windows/macos/solaris/aix): Linux
- New machine architecture (e.g. x64/aarch32/arm32/ppc64/ppc64le/sparc): aarch64
- Provider (leave blank if it does not matter): OSUOSL / Linaro
- Desired usage: Performance testing
- Any unusual specification/setup required: Not virtualised
- How many of them are required: 1/2
Please explain what this machine is needed for: Replace AWS RHEL7 system which is the only one available for the perf test jobs (Also that one is not currently used for anything else)
@smlambert If we do this the performance test results will not be comparable before and after. Will that cause any problems, or are we not looking at the results closely enough at the moment for it to be a problem?
We are only keeping 90 builds worth of perf history at the moment, so I do not think this will have a big impact, as we can build up history on the new set of machines in a short space of time, and as you correctly state, we've not moved into our intended 'phase 2' plan of deeper analytics for our perf test results yet.
Running the following on build-osuosl-ubuntu2204-aarch64-1 with a view to switching over:
- sanity.perf PASSED
- extended.perf Failed as hostname wasn't resolvable in /etc/hosts - I've renamed the machine to test-osuosl-ubuntu2204-aarch64-1 and fixed the hosts entry. Running again:
- extended.perf
- sanity.perf
/etc/hosts is getting overwritten on reboot by an entry that doesn't match /etc/hostname. I've adjusted /etc/cloud/cloud.cfg to comment out update_etc_hosts so the hostname resolution doesn't get lost as it won't overwrite /etc/hosts:
Pass - have enabled ci.role.perf on those machines and marked the AWS on offline.
There may be some argument for testing on Graviton machines, and RHEL on aarch64, but at the moment I'm happy to decommission