-
Notifications
You must be signed in to change notification settings - Fork 541
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
[bug] experiencing >10x slower download on v4 #376
Comments
I have a similar issue too on v4. I have a very old intel mac mini that's downloading an artifact in 7 seconds. I have a newer M4 Mac mini and the VERY SAME artifact is taking 3 minutes plus to download. Makes no sense the M4 should be way faster |
For v4, the download happens between the runner and Azure Blob Storage directly. Are you using self-hosted runners or hosted runners? |
I'm using a self-hosted Windows runner. |
i dont know what the hell you guys are talking about, im here justo to show my wife that i am working right now so that i can sleep for few minutes. this is crazy |
@jiaanlu I would advise you to work with your network admin and see if traffic to Azure Blob accounts are throttled. If you hit https://api.github.com/meta, you will see all the |
What happened?
My workflow has 2 jobs A and B.
Job A uses upload-artifact@v4 to upload an artifact ~80M
Job B uses download-artifact@v4 to download the artifacts.
This workflow has been up running for months, and usually it takes up to 3mins to complete download depending on network quality. But in recent days, it suddenly takes 30mins to complete. It happens with high frequency.
What did you expect to happen?
Each time the download time for the artifact should be approximately the same.
How can we reproduce it?
The repo is private...
Anything else we need to know?
No response
What version of the action are you using?
actions/download-artifact@v4
What are your runner environments?
self-hosted
Are you on GitHub Enterprise Server? If so, what version?
No response
The text was updated successfully, but these errors were encountered: