Nuget package sources proxy

Topics: General
Dec 19, 2013 at 11:10 AM
Hi guys,

Is there a list of possable Sources proxies?

If we delete the pakages folder and run another build from our US Office the get is pretty quick.
But from our France Office it's about twice as long. We're using fiber in our paris office so i think this comes from lag over the Atlantic.

So Is there a European or even better a Western Europe proxy for "https://www.nuget.org/api/v2/"?
Or is this supposed to be handled by the API?
Or better yet can i create a package proxy?
Developer
Dec 19, 2013 at 2:20 PM
This question is better answered by the NuGet Gallery folks - https://github.com/NuGet/NuGetGallery. That said, the packages are distributed via Azure's geo distributed CDN, but the API surface currently is not geo-distributed. This would explain the slowness. You could look into https://myget.org. They have package proxying features but I'm not sure where their servers are located.

That said are you seeing the slowness when you're doing package restore? NuGet caches packages in %LocalAppData%\NuGet\Cache and uses files in this directory for restore. Unless this folder is not getting populated, connectivity to the gallery shouldn't matter.
Dec 19, 2013 at 3:47 PM
Thanks

Actually i dissabled the TFS linking with the package folder and it's much faster now.
http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages

So it looks to be a combo issue with TFS also being in the US and VS needing to call home to create the insert or update lock.