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!

    High CPU usage when acceding http://{proget-server}/nuget/nuget/Packages

    Scheduled Pinned Locked Moved Support
    progetnugetiis
    2 Posts 1 Posters 33 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

      Hi,

      Everytime a user access this url http://{proget-server}/nuget/nuget/Packages , the IIS process (w3wsp.exe) jumps to the roof taking all the CPU of the machine. The RAM is also rising.

      Image Text
      This cause our nuget feeds to stop working and the page at that address then display :

      Server Error

      502 - Web server received an invalid response while acting as a gateway or proxy server.

      There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.

      Our host have 8 GB of RAM and 4 cores. We have over 2000 nuget packages. We were wondering if this is an issue or just need more ressources to be able to list all those nuget packages. Please advise.
      Thank you

      Product: ProGet
      Version: 5.1.4

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

        Assuming you don't any server misconfiguration or SQL Server latency issues, then the biggest performance bottleneck tends to be the network.

        Each client/user will make dozens or hundreds of simultaneous requests, often using machines more powerful than the server, and these requests can be expensive... particularly if you're using connectors... because they have to be forwarded to another server. These requests "pile up" and eventually, the underlying infrastructure can't handle it (IIS, network card, etc), and you start getting timeouts like that.

        This is where load-balancing comes in, and is pretty important in your configuration as you add users and packages.

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

        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