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

First run of az-cli is slow #10110

Open
6 of 14 tasks
lanni-energinet opened this issue Jun 24, 2024 · 1 comment
Open
6 of 14 tasks

First run of az-cli is slow #10110

lanni-energinet opened this issue Jun 24, 2024 · 1 comment

Comments

@lanni-energinet
Copy link

lanni-energinet commented Jun 24, 2024

Description

For quite some time we have been impacted by poor performance due to the nature of az-cli's command and module caching on it's first run. It would seem that az-cli was not written with ephemeral runners in mind, and it doesn't look like they could change this easily. Hence why we are opening this issue here.

We can see that the issue is fixed on windows images as a simple warmup has been implemented

Can you please implement a simple warm up like on the windows runners?

From a sample of our logs we have measured the following impact
Minimum 2 s
Maximum 31 s
Average 5 s

We estimate wasting roughly 6500 minutes per month which is more than 10% of our of total usage

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 11
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240609.1

Is it regression?

no

Expected behavior

A build-in warmup in the ubuntu image creation similar to the windows image

Actual behavior

No warmup

Repro steps

None needed

@kishorekumar-anchala
Copy link
Contributor

HI @lanni-energinet ,

Thank you for bringing this issue to us, we are investigating on this issue and we will update you on this issue after our findings.

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

2 participants