actions / cache

Cache dependencies and build outputs in GitHub Actions
MIT License
4.51k stars 1.2k forks source link

Cache save is too slow in container job #1126

Closed asvataa closed 1 year ago

asvataa commented 1 year ago

Hi There!

Cache save is too slow in container job

There is screenshots

  1. Save cache without container = 4 sec.
Снимок экрана 2023-02-28 в 12 18 23
  1. Save cache in container without cpu tuning = 16 sec.
Снимок экрана 2023-02-28 в 12 20 06
  1. in container with cpu tuning up to 2 core = 11 sec.
Снимок экрана 2023-02-28 в 12 20 27

All files was the same for all tests

I don't understand where is a problem? Why is it become slowly?

kotewar commented 1 year ago

Hi @asvataa ,

Can you please share sample workflow runs (in a different repo if its private with minimum code to replicate the issue) with runner diagnostic and step debug logs enabled so that we can take a closer look? Thanks.

asvataa commented 1 year ago

@kotewar Hi,

https://github.com/asvataa/cache-save-issue/actions/runs/4291052955/jobs/7475762430

Phantsure commented 1 year ago

@asvataa Can you please provide a workflow run with debug logs? For that you may need to enable a secret. Follow this guide: https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging#enabling-runner-diagnostic-logging

asvataa commented 1 year ago

@Phantsure this is it? https://github.com/asvataa/cache-save-issue/actions/runs/4310600493

Phantsure commented 1 year ago

@asvataa Logs in purple here are debug logs. Have to set ACTIONS_STEP_DEBUG as true in repository secrets or you can re-run workflow with a check to enable debug logs:

Screenshot 2023-03-02 at 3 50 43 PM
asvataa commented 1 year ago

@Phantsure my bad https://github.com/asvataa/cache-save-issue/actions/workflows/build-nodejs.yml

github-actions[bot] commented 1 year ago

This issue is stale because it has been open for 200 days with no activity. Leave a comment to avoid closing this issue in 5 days.

github-actions[bot] commented 1 year ago

This issue was closed because it has been inactive for 5 days since being marked as stale.