sqsever exe w3wp exe occupies 100 more CPU

You can open the task manager, see which program occupies a larger proportion, if you suspect that there is a problem with that program, reinstall it, if there is still a problem, reinstall the system and try it.

Occupies a large amount of CPU for a long time, and this situation should be caused by problems such as dead loops in the ** program. Under IIS6, memory and CPU usage often cannot be released in time, resulting in slow server response speed.

Ways to fix excessive CPU usage:

1. Configure a separate application pool for each ** in IIS. That is, they do not affect each other.

2. Set the CPU monitoring of the application pool, no more than 25% (4CPU for the server), refresh every minute, and turn off when the limit is exceeded.

3. Set the ** time of the application pool, the default is 1720 hours, which can be modified according to the situation. Then set how much memory is occupied (such as 500M), it will automatically ** memory.

Don't ask this question in the hardware area, there are definitely not many people who answer it! Personally, I think the possibility of being attacked is still not very large, it may be because of a few more nodes, low efficiency in program execution, high CPU occupation, Microsoft's is not the first choice for most network administrators, there are a lot of bugs, and there will be results if you study it slowly (not by your side, it is difficult to find the cause of the problem, and it will be solved if you find the cause).

IIS Management -**-Properties, enable the date logging checkbox, select the W3C extended log file format, and click Properties -select hourly.

Wait a while and check the day log.

You can analyze what caused it from the logs.

It's your ASP program, the program has an endless loop, but it's also possible that it's poisoned.

This can also happen if someone is generating a static file (which is quite large).

It's OK to finish him, bird.

Is yours a server?,It's good to say that the IIS service is turned off; If it is, it is normal to occupy CPU and memory, and if you feel struggling, you can upgrade the server hardware.

Refer to the book of the year Lu Dou Kaozhou open.

In this case, there are only viruses,

The following ** to 8173789 on 2007-12-27.

The normal operation of the server cup should generally be below 60%, sometimes the cup fluctuates a lot, or the server is suddenly very stuck, or very slow. Looking at the task manager, you can find that a lot of CPU is consumed, and immediately after the end there are new ones that appear to account for the CPU, and the administrator is in this situation. Had to restart the IIS service, and oddly enough, everything worked fine after restarting the IIS service, but probably after a while, the problem reappeared.

Direct cause: One or more access databases are corrupted during multiple reads and writes, and when Microsoft's MDAC system writes this corrupted access file, the asp thread is in the block state, and other threads can only wait, IIS is deadlocked, and all CPU time is consumed.

Workaround:1

Set up multiple application pools in the IIS Manager and add the virtual hosting sites to the application pools. In the case of multiple application pools, one file is generated for each application pool. You can view the usage of all occupied CPUs through Task Manager.

By opening an application pool through the IIS Manager, you can stop the application pools one by one. While stopping the application pool, observe in the task manager which CPU utilization suddenly decreases and the CPU utilization returns to normal. This will tell if there is a problem with that application pool.

Multiple application pools can then be created, each corresponding to a site. In this way, by stopping the application pool one by one, you can determine which ** is the problem. The most problematic tends to be access files of counter classes, such as:

Workaround:2

The CPU usage query method is the most troublesome problem for many web providers, and the task manager often occupies too high the cup, resulting in the entire server being affected. The solution is as follows:

1.Open the task manager first, and end the process when you find that the account is high.

2.In My Computer - Management - Event Viewer - System - you will find the error report that is off, record the name of the program pool, and then record the specific time. (Such as.)

3.Security on top of the system. Find the time (e.g., users who have logged in.)

4.Open IIS to find the program pool queried in 2, and 3 to query the logged in users, take the intersection, you can accurately find out which web point station cup

is a process running in the iis6 process pool. You first check the pid of this process in the explorer and then run iisapp p pid number under cmd to find out the process pool, and then check which ones are included in the process pool in iis, and close these.

W3WP is a process pool, and your high temporary usage rate is due to the existence of a large number of visits** (we** are in this situation now, it is good to use load balancing to use multiple servers to divert traffic) Check whether there is a large amount of traffic in the VPS**.

Shutting down is equivalent to restarting the process pool, and he will start it himself.