Replies: 4 comments 4 replies
-
Looking at the timing data, it seems the 'Extracting ..' steps are really slow. |
Beta Was this translation helpful? Give feedback.
-
A long time ago it was decided that setup-ruby would install the compiler, build tools, and packages needed to build Ruby on Windows. Ubuntu & macOS images have all these items preinstalled, Windows images do not. Many repos may lack the experience with Windows to install the tools (the tools vary by Ruby version), so by preinstalling them, a common comment is 'it just works'... |
Beta Was this translation helpful? Give feedback.
-
One possibility, if you don't need to compile any gem native extensions, is to use: with:
windows-toolchain: none That should speed it up quite a bit. |
Beta Was this translation helpful? Give feedback.
-
Are you using a GitHub runner (not self-hosted)? I think I might have a fix. Currently, GitHub runners have both a HDD and an SSD. The Ruby 7z files are being extracted to the HDD for CRuby versions that aren't head builds. Looking at a recent CI run, Ruby 3.3.6 took 26.0 seconds to extract to the HDD, and Ruby ucrt/head took 2.5 seconds to extract to the SSD. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your excellent work.
I'm wondering why installing ruby and gems with ruby/setup-ruby@v1 is so much slower on windows? An example:
windows-latests: 2m18s
ubuntu-latest: 2s
macos-latest: 3s
Is this normal or is something wrong with my setup?
Thank you!
Emil
Windows log:
Linux log:
Beta Was this translation helpful? Give feedback.
All reactions