• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2132
  • Last Modified:

MS IIS6 - how to tune the server reduce w3wp.exe CPU picks?

In my server win 2003 which is running IIS6 and serving sites there is a problem.

Once after a delay there is a pick hour of traffic w3wp.exe takes 100 CPU%.

Reading the article

I understood that that there is JIT compiler in .NET and IIS once new process started compillation is going on and taking the time, cpu and mem.

So the question how to make tunings that avoid such process burst activities?
How to configure IIS6 to keep process always up?
Or may be another configuration helps here?

Please advice.

  • 2
  • 2
2 Solutions

IIS 6.0 F1: Application Pools Properties - Performance Tab- Maximum CPU use (percentage)
longjumpsAuthor Commented:
And how to tell IIS that processes never down?

W3WP.exe is running at high cpu utilization
seec comments of sunilyadav165
longjumpsAuthor Commented:
Yes. I saw his doubts about separation of dev and prod enviroment and tuning and reference for new McAffee feature buffer protection.

However it is not so answering my questions:
1. Is it legitimacy  to configure IIS6 to keep process always up?
2. If I limit CPU usage by 80% will this help keeping healthy server and IIS state?
3. If I define 4 processes per Application Pool will this help distribute load?
4. BTW: If I have 1 process per pool meeting that all request are processed sequencually by this w3wp or may be it has execution threads. If so how to configure these threads?

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now