Skip to content

Provision benchmarking machines #298

Open

Description

@mdboom

The next step in setting up benchmarking infrastructure is to actually purchase the hardware and get it to OSUOSL.

I have some notes about what I think we should buy here:

https://docs.google.com/document/d/1s0fGsyeopjAS_sI-Og7ySMFii4FmgshaWZL3eRWpqfY/edit?usp=sharing

We should coordinate with OSUOSL and Ee Durbin on what their views are on this.

Activity

  1. brandtbucher commented on Aug 25, 2025

    @brandtbucher
    Member

    Just one comment on the doc: for full tier 1 coverage, we would technically also need to include an AArch64 Linux machine. Obviously this matters a bit less than the other two, but I'd personally prefer to expand this platform coverage rather than the current "stretch" target of a second x86-64 Linux machine.

    Or maybe Arm already has plans here?

  2. mdboom commented on Aug 25, 2025

    @mdboom
    Author

    ARM Inc. is still planning to generously support this hardware. In terms of resiliency, though, having the PSF own it would be better, so you make a good point.

  3. diegorusso commented on Nov 19, 2025

    @diegorusso

    I've just pointed to this issue. I want to confirm that the AArch64 machine is up and running. Currently is serving as buildbot worker for bigmem builds and it is running daily benchmarks for speed.python.org.

    This machine was donated from Arm to the PSF and at the moment Arm is hosting it. The longer term plan is to ship it to wherever the PSF finds to be a good place for hosting it.

    Specs are. AmpereOne:

    • 192 Ampere 64-bit, Arm v8.6+. 3.6Ghz, L2: 2MB/core, L1: 16KB ICache/core, 64KB DCache/core
    • 512 GB (8 x 64 GB DDR5 Registered (Buffered) @ 5200 MT/s)
    • 1x1.7TB NVMe, 1x3.5TB NVMe
    • 2x10Gbps
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions