Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Very slow NPM dependecies resolving

    Scheduled Pinned Locked Moved Support
    proget
    3 Posts 1 Posters 23 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      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

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by apxltd

        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...

        See How to Prevent Server Overload in ProGet to learn more.

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          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...

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation