Github action cache is really slow

Following is my config for my private project cache.

      - name: Cache meta_api Rubygems
        uses: actions/cache@v2
          path: |
          key: Gemfile.lock-${{ hashFiles('components/meta_api/Gemfile.lock') }}
      - name: Cache IoT Rubygems
        uses: actions/cache@v2
          path: |
          key: Gemfile.lock-${{ hashFiles('components/iot/Gemfile.lock') }}
      - name: Cache OTA Rubygems
        uses: actions/cache@v2
          path: |
          key: Gemfile.lock-${{ hashFiles('components/ota/Gemfile.lock') }}
      - name: Cache API Rubygems
        uses: actions/cache@v2
          path: |
          key: Gemfile.lock-${{ hashFiles('components/api/Gemfile.lock') }}

my workflow is working, but in most of time, it really really slow, following is some screenshot

Please check, thank you.

BTW: i don’t know why, when i test this feature on a public repo, the speed is better,
so, for our Pro user, there exists some limit for cache queue?

1 Like

We have the same issue. Caching Maven’s m2 is about as fast as just downloading all of the hundred dependencies over and over again.

EDIT: Previous run was at 27 seconds, now one run was at 13 minutes while the next run was fast again. Same cache. What can be the reason for this? Inconsistent runner hardware?

Hi @zw963,

Glad to see you in Github Community Forum!

actions/cache is an official github action, and i find there is already an issue raised.

Based on the embeded link, this could be caused by the network issue, the high latency requests from the cloud storage provider.

Sorry you experienced this, it’s recommended to add your comment on the issue, github dev team will check and help to improve.

In the meanwhile, you can also raise a feedback ticket here where github product manager will take a review, to promote the action improvement.


1 Like

Hi @zw963 @meiswjn,

A new version @v2.1.0 (the @v2 tag also points to this release) is released, could you please check and confirm whether the cache speed is fine now?

More details here:



Issue has been resolved for us, cache is very fast now. Thanks!