You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
time git clone --depth=1 https://github.com/pre-commit/pre-comit (on a windows-latest runner): .802s
I get that windows tends to be slower than the linux runners, but this feels unacceptably slow. even linux feels slower than it should be (actions/checkout@v3 in pre-commit takes 2 seconds there)
here's the yaml that I used to test this (will probably delete the empty repo above since I just wanted to see how long it takes):
on: pushjobs:
main:
runs-on: windows-lateststeps:
- uses: actions/checkout@v3
- run: | set -x time git clone https://github.com/asottile/test-plz-ignore --depth=1 time git clone https://github.com/pre-commit/pre-commit --depth=1 shell: bash
The text was updated successfully, but these errors were encountered:
I profiled the actions/checkout@v3 on Windows runners a bit with ETW. Looks like even loading the node.exe PE image from disk to memory could stall the workflow for a couple of seconds! On the graph, only during 11s - 23s are git and git-remote-https doing real useful work. The first ten seconds are all overhead on something.
this action adds significant overhead to getting set up, I don't really know why but I tried comparing it in an empty repo against
time git clone ...
time git clone --depth=1 (an empty repo from github)
(on awindows-latest
runner):.613s
time git clone --depth=1 https://github.com/pre-commit/pre-comit
(on awindows-latest
runner):.802s
I get that windows tends to be slower than the linux runners, but this feels unacceptably slow. even linux feels slower than it should be (
actions/checkout@v3
in pre-commit takes 2 seconds there)here's the yaml that I used to test this (will probably delete the empty repo above since I just wanted to see how long it takes):
The text was updated successfully, but these errors were encountered: