One of the peskiest problems in maintaining a web server is IIS processes that bloat. The whole server runs like a dog and when you check the Task Manager, you find that one service is taking up 80% of the CPU cycles and half a GB of RAM...
You have the PID of the process through Task Manager, but I used to have difficulty nailing down which process was causing the problem from there.
The simple trick is to run the command line command iisapp. This script simply lists all running application pools and their PIDs. It lets you pick the faulty PID straight away (as long as you can remember the name of the command...)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment