Migrate from old bare metal github self-hosted runner to new one

[trask]

See #3310 for background.

Old runner:

• name: oracle-bare-metal-64cpu-512gb-x86-64
• 512gb memory
• Oracle Linux 8

New runner:

• name: oracle-bare-metal-64cpu-1024gb-x86-64-ubuntu-24
• 1024gb memory
• Ubuntu 24

I realize this could have some impact on benchmark baselines, so please post on this issue once you have migrated and are comfortable with the old one being removed.

[scottgerring]

Looks like the first run on otel-rust flaked out talking to the runner.

Re-triggered here

edit 12:45 CET: The new job hasn't been picked up by the runner yet; is it online?

[trask]

Thanks for reporting it! Not sure what happened, but the runner was indeed offline. It's back online now 🤞

[jack-berg]

How often do we expect this to happen? Trying to think through whether I need to come up with a general purpose solution to mark / flag that the underlying bare metal runner has changed. I intend to update java documentation on opentelemetry.io to reference our performance benchmark page, and will need to contextualize things like this to avoid confusing readers.

[trask]

did the switch have any affect the Java benchmark numbers?

we were sort of lucky this time that the same hardware was still available (just more memory, though guessing 512g wasn't a bottleneck before 😄), but that may not always be the case

as far as how often we'll need to at least update O/S, I'd guess ~4 years, e.g. Ubuntu 20 -> Ubuntu 24

not sure why we were on such an old Oracle Linux version (2019), probably was just the default when we initially set it up