Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows: prefer git cloning registries (close #2014) #2175

Merged
merged 1 commit into from
Oct 29, 2020

Conversation

StefanKarpinski
Copy link
Member

Since untarring a tarball like the registry is so slow on Windows,
we prefer to git clone registries instead. Git is slow on Windows
as well, but git updates are faster since git only updates the
files that need to be modified, which is much faster than unpacking
a whole new registry.

Since untarring a tarball like the registry is so slow on Windows,
we prefer to git clone registries instead. Git is slow on Windows
as well, but git updates are faster since git only updates the
files that need to be modified, which is much faster than unpacking
a whole new registry.
@DilumAluthge
Copy link
Member

Can we backport this to 1.6?

@StefanKarpinski
Copy link
Member Author

Can and should. To 1.5 also, if we're going to do any more releases off that version (which we should, imo).

@StefanKarpinski StefanKarpinski merged commit 7297ccf into master Oct 29, 2020
@StefanKarpinski StefanKarpinski deleted the sk/prefer-registry-clone-on-windows branch October 29, 2020 20:01
@KristofferC
Copy link
Member

I wonder if not #2186 caused a lot of the slowness..., not untarring. Probably a combination of both.

KristofferC pushed a commit that referenced this pull request Nov 1, 2020
Since untarring a tarball like the registry is so slow on Windows,
we prefer to git clone registries instead. Git is slow on Windows
as well, but git updates are faster since git only updates the
files that need to be modified, which is much faster than unpacking
a whole new registry.

(cherry picked from commit 7297ccf)
@StefanKarpinski
Copy link
Member Author

Probably both.

@j-fu
Copy link
Contributor

j-fu commented Nov 13, 2020

Found this one: microsoft/Windows-Dev-Performance#27 - there seems to be a possible communication channel to the windows devs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants