Very slow NPM dependecies resolving

We have been using Proget for a while now and we are happy with the general functionality, but I was wondering if we have a problem with performance.

When we want to do npm installs for our projects, it takes very long to download all the packages from Proget inside our local domain. The server on which it is installed is a virtual machine and it has enough memory to hold all the data Proget is demanding ( in my opinion)

At the moment we are having 10min install times to get all the packages on the build system. We don't have too many packages for a typical SPA, but of course they include lots of small ones.

If we do the same thing straight to the npm registry itself, it doesn't seem to do as much communication as Proget does.

What should the expected performance be of Proget against the registry website itself.

I was hoping it to be very fast, but that doesn't seem to be the case...
Any tips on how to improve the performance would appriciated.

Product: ProGet
Version: 4.4.2

The server on which it is installed is a virtual machine and it has enough memory to hold all the data Proget is demanding ( in my opinion)

Yeah... you would think something as simple as this wouldn't require so much resources, right??

Welcome to npm. To be even more amazed, just attach Fiddler, and see exactly how hard your workstation is hammering ProGet for even the simplest of requests :)

ProGet will actually outperform a npm enterprise repository running on the same hardware, hands down. The public registry, npmjs.org, requires a massive server farm to run. It also doesn't have connectors, authentication, licensing filtering, etc, so it's always going to be faster.

The only way to improve performance is to improve hardware and get into load balancing. Or wait until someone, someday writes a better client...

Thank you for this amazing honest answer,

Coming from .NET and Nuget, i've been enjoying the struggles of npm and it's evil offspring for a while now, haha

All developers swear it's so good, until we need to make builds from their code...