guardicore
Build performance of C2D instances
Spike
Objective
C2D GCP instances have faster processors than C2 instances. Upgrade the build nodes to C2D instances and record how long each artifact takes to build. Switch the machines back to C2 instances once you're done.
Output
A report comparing the build times before and after the switch to C2D for each artifact.
Time Remaining
0d
These are the results from when we switch from on-prem to C2 instances on GCP.
Linux agent On-Prem: 04min 34sec (274 seconds) GCP C2: 02min 13sec (133 seconds)
Windows Agent On-Prem: 05min 30sec (330 seconds) GCP C2: 01min 53sec (103 seconds)
AppImage On-Prem: 04min 12sec (252 seconds) GCP C2: 02min 09sec (129 seconds)
Docker On-Prem: 05min 2sec (302 seconds) GCP C2: 02min 20sec (140 seconds)
MSI On-Prem: 17min 0sec (1020 seconds) GCP C2: 04min 54sec (294 seconds)
Critical path: On-Prem: 22min 30sec (1350 seconds) GCP C2: 07min 7sec (427 seconds)
For testing the builds with C2D machines, we're going to have to create new machines in a different region and then change the Jenkins scripts to use those, which is more effort than is worth taking for this right now. We can't change the existing ones right now because they need AMD processors (reference) for which we need the machines to be in a different region. It looks like they're adding C2D instances to new zones over time, so we should try this again in a few months.
