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!

    Proget with npm feed use massive a amounts of CPU/RAM

    Scheduled Pinned Locked Moved Support
    progetnpm
    4 Posts 1 Posters 14 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

      Hello.
      I upgraded to Proget 3.6.1. to get rid of crashes in ProGet and now face other issues. Our npm feed is unusable since when the Npm is queried the ProGet service process starts to use enough memory to make the system very slow. My machine has 4GB of RAM and the process is allowed to consume about 3.2GB of it. This is a bug I assume?

      Some things I have discovered

      • Reproducible in versions 3.5.5, 3.5.8 and 3.6.1
      • Before npm feed connector is indexed the peformance, the above behavior is not seen
      • While indexing I could see lots of indexing errors. I can't find that log now but I think it was complaining about not finding a 'versions'-tag

      Let me know if I should add some logging or can help in any other way.

      Niklas

      Product: ProGet
      Version: 3.6.1

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

        When using an npm connector, the entire npm metabase must be downloaded from npmjs.org, and then indexed. This can take 5-15 minutes. After that, only incremental download/indexes occur.

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

          I don't think this is the only thing happening here.

          The proget service is holding on to every little ounce of memory in the machine (while not responding to requests) and doing so for, as far as I can tell, forever.

          Is there something else we can do to troubleshoot? It's not usable at the moment for us.

          Thanks for the answer,
          Niklas

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

            We have not had other users report this problem, nor have we seen it during testing.

            You can try running the service interactively (just stop the WIndows Service, then run the .exe file), and see what happens.

            Also worth noting, make sure that all the errors in the log are deleted before the packages start indexing again.

            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