- Issue created by @wim leers
- Merge request !6241Borrow a test performance optimization from @secretsayan over at... ā (Open) created by wim leers
- š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
However, looking at https://docs.gitlab.com/runner/executors/kubernetes.html#cpu-requests-an..., I think
service_cpu_requestis the name of the setting at the Kubernetes level.AFAICT we should be using
KUBERNETES_SERVICE_CPU_REQUESTinstead. Let's see if the above made a difference or not first. š - š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
Hm, 96 seconds vs 110 s, 111 s, 110 s, in other MRs I'm working on today.
So it does appear to improve things, but not by multiple minutes like @secretsayan was seeing.
~12% faster.
- š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
Well well well ā¦ 4b8e7111 got me to 115 s.
So maybe it did work after all? š¤
Retesting both jobs to see if the difference remains.
Queued both simultaneously:
SERVICE_CPU_REQUEST: https://git.drupalcode.org/issue/drupal-3415813/-/jobs/664260KUBERNETES_SERVICE_CPU_REQUEST: https://git.drupalcode.org/issue/drupal-3415813/-/jobs/664259
Which will win the race? š I'll repeat this a few times to verify reproducibility.
