Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. ASP.NET performance problem

ASP.NET performance problem

Scheduled Pinned Locked Moved ASP.NET
questionasp-netcsharpsysadminperformance
2 Posts 2 Posters 0 Views 1 Watching
  • 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.
  • P Offline
    P Offline
    Paul Horstink
    wrote on last edited by
    #1

    I have a Windows2000 based server, running many ASP.NET application. Occasionaly performance of the servers starts to degenerate enormously, and users start calling/complaining. When I check I see the process 'aspnet.exe' taking up a huge amount of CPU. Question now is, how do I find out which application is causing this problem? Any suggestions?

    N 1 Reply Last reply
    0
    • P Paul Horstink

      I have a Windows2000 based server, running many ASP.NET application. Occasionaly performance of the servers starts to degenerate enormously, and users start calling/complaining. When I check I see the process 'aspnet.exe' taking up a huge amount of CPU. Question now is, how do I find out which application is causing this problem? Any suggestions?

      N Offline
      N Offline
      N a v a n e e t h
      wrote on last edited by
      #2

      AFAIK, there is no efficient way to find out which application is causing the problem. You can just check the event log for warnings and error messages, that might help you. Or analyze which website is getting more traffic and doing some heavy operations. That would be the one causing problem.

      All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia My Website | Ask smart questions

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups