Nothing Special   »   [go: up one dir, main page]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New worker request: <diegorusso-aarch64-bigmem> #473

Open
diegorusso opened this issue Mar 8, 2024 · 9 comments
Open

New worker request: <diegorusso-aarch64-bigmem> #473

diegorusso opened this issue Mar 8, 2024 · 9 comments

Comments

@diegorusso
Copy link
Contributor
diegorusso commented Mar 8, 2024

Username

diegorusso

GitHub username

No response

Name

Diego Russo

Email address

diego.russo@arm.com

Password status

I need a new owner password

Processor architecture

aarch64

Operating System

Ubuntu 22.04

Anything special about the worker?

This machine is an aarch64 Equinix machine and it is currently used to run benchmarks to be uploaded to speed.python.org.
Given its spec, we'd like to run also bigmem tests.
Tagging @ambv for visibility

@zware
Copy link
Member
zware commented Mar 8, 2024

Hmm, if it's a benchmark runner, do we really want it running a buildbot as well? It seems that would impact its ability to run benchmarks effectively, or would require routinely stopping the buildbot worker process.

@diegorusso
Copy link
Contributor Author
diegorusso commented Mar 8, 2024

We have set up the machine with cpu isolation. The machine has 80 cores and we have isolated the last 14 cores for running benchmarks: to be precise we run benchmarks just on the odd cores in the range 65-79 (65, 67, 69..) using cpu affinity.

Daily benchmarks are run at midnight (UTC) only, the rest of the time the machine is idle.

The aim is to maximise the use of this machine. If we want to be on the safe side we could pause buildbot jobs 2 hours before and after midnight so it won't be scheduling jobs when benchmarks will be running.

@zware
Copy link
Member
zware commented Mar 8, 2024

Ok. I'm no expert at benchmarks, so if that configuration is deemed sufficient from that side of things, I'm ok from the buildbot side of things :)

Can you create a PR adding the public configuration? #404 should be a reasonable template to follow, though there may be some extras needed to enable bigmem testing.

@itamaro
Copy link
Contributor
itamaro commented Mar 10, 2024

@diegorusso I created a new owner password and emailed it to you.

@vstinner
Copy link
Member

Related PR: #474

@diegorusso
Copy link
Contributor Author

Thanks @itamaro. I confirmed I received it.

@diegorusso
Copy link
Contributor Author

I have my hands blocked until this https://discuss.python.org/t/top-level-license-not-present-on-some-repos/47973 gets resolved.

@itamaro
Copy link
Contributor
itamaro commented Jun 16, 2024

@ambv were you planning to add license and CLA bot?

@ambv
Copy link
Contributor
ambv commented Oct 10, 2024

MIT license added as all contributors were reached for acknowledgement and provided it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants