Announcement

Collapse
No announcement yet.

Over CPU - 2003 Server Std.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Over CPU - 2003 Server Std.

    Hey guys,

    little background:
    2 win 2003 servers, clustered together in a small 5 servers farm.

    in the last two days, suddenly the servers (both of them) starting to gather high cpu rate and the only thing that can stop it is a IIS restart.

    the servers have more than 100 domains, and this behavior is not regular.
    how can i check which domain is using more cpu from the other?

    or any other ideas?

    thank you!

  • #2
    Re: Over CPU - 2003 Server Std.

    How many app pools do you have configured? One per site or a shared global one?

    If you configure one per site you can enable cpu throttling on the app pool so it doesn't use more than it's share.

    If you use Process Explorer, you can inspect the w3wp processes. So you'll need to have a seperate app pool for each site for this to work. In that process, you can see the command line, which will include the app pool for that process. It will look something like this:
    Code:
    c:\windows\system32\inetsrv\w3wp.exe -a \\.\pipe\iisipm84880310-cf11-4d4f-96c5-756a9ebeab1c -ap "ExchangeApplicationPool"
    This way you can see which app pool is the offending cpu hog and throttle it.

    Edit: Clustering might complicate this and I haven't had time to really think through whether this will even work in that situation.
    Last edited by ahinson; 1st January 2009, 15:58.
    Andrew

    ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

    Comment


    • #3
      Re: Over CPU - 2003 Server Std.

      I agree. Ypu should configure each web site in Isolated mode (for IIS 5) or create a unique app pool for each web site (IIS 6), which will create a unique app pool for each web site and launch each web site in it's own dllhost process. You'll then be able to see which dllhost process is consuming the CPU and track down the app pool and web site based on the PID of the dllhost process.

      Comment


      • #4
        Re: Over CPU - 2003 Server Std.

        the app pool is shared for all the websites.

        is there any other way to analyze it?

        Thanks!

        Comment


        • #5
          Re: Over CPU - 2003 Server Std.

          Yes, do what ahinson and I have suggested.

          Comment


          • #6
            Re: Over CPU - 2003 Server Std.

            Originally posted by iQuad View Post
            the app pool is shared for all the websites.

            is there any other way to analyze it?

            Thanks!
            When you use a shared app pool all of the cpu time and memory for each site that uses that app pool are lumped together and afaik there is no way to distinguish one site from another in that case.
            In task manager, what process is using the most cpu time? Just because cycling IIS fixed the issues doesn't mean that's it's not one of IIS's core processes [inetinfo.exe, dllhost.exe or svchost.exe] vs an app pool process [w3wp.exe].

            If it is one of the core processes it's probably not a specific site that's causing the increased cpu utilization because an individual site and the web server itself are isolated from each other so a downed site doesn't bring down the web server and with it all sites. With IIS 6, isolation mode is the default.
            Last edited by ahinson; 1st January 2009, 17:08.
            Andrew

            ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

            Comment

            Working...
            X