3 ms·
My read is that there's a refresh job that's doing hundreds of full git clones even for packages that don't have users. Package with approx. zero users: https:
by 8organicbits 4y ago
My read is that there's a refresh job that's doing hundreds of full git clones even for packages that don't have users.
Package with approx. zero users:
https://github.com/golang/go/issues/44577#issuecomment-851079949 https://github.com/golang/go/issues/44577#issuecomment-85107...
Full clones:
https://github.com/golang/go/issues/44577#issuecomment-789242343 https://github.com/golang/go/issues/44577#issuecomment-78924...
They disabled refreshes (for someone else) to fix the issue:
https://github.com/golang/go/issues/44577#issuecomment-862719746 https://github.com/golang/go/issues/44577#issuecomment-86271...
So maybe there is some caching happening between the user and the mirror, but the mirror is hammering the origin with much more load than should be needed.