IIS using 100% of CPU - add a processor ?

[FredWagner]

IIS 5.0 running on 2.4Ghz Pentium 4, with 1.0GB of RAM; Gigabit network interface into the server, though the clients are across a 57MB RF link. we use Kofax Ricochet 1.1.64, which is a web based imaging front end. Several times a day, INetinfo.exe goes to 100% CPU utilization, and a couple of other functions on that server become completely non-responsive until IIS's peak subsides.
Would adding a 2nd processor to the server help with the INetinfo.exe load ? or would we be able to have Inetinfo just use one processor, and let the other processed use the other ?


Fred Wagner
frwagne@longbeach.gov

 

[newmediaguy]

Hi

What are you trying to run on the server SQL Server/ASP etc

If you set IIS up incorrectly for your app it will max out its VM for the process. Bad SQL or unterminated loops wont help either in ASP as they run the buffer out.

......might not help.



Glen
Conception | Execution

 

[FredWagner]

We have SQL on two other servers, none on this particular one with the IIS load. I'll check the System Admin manual for the app and see if there were some settings for IIS that could have been missed. Thanks!

Fred Wagner
frwagne@longbeach.gov

 

[zaznet]

Have you applied all the latest SP's and Hotfixes?

inetinfo.exe should not run away with the CPU that often, I mean a single P4 2.4Ghz just isn't that cute...

You also might find this link useful.

Microsoft IIS: Troubleshooting High CPU Utilization

Nathan aka: zaz (zaznet)
zaz@zaz.net

http://www.zaz.net/

 

[TonyKhela]

Do you have index server running??

 

[FredWagner]

As a matter of fact, indexing WAS turned on on that box. I always check that on workstations, never thought to check it on this server. That box is running Kofax Ascent and Ricochet, but I don't think indexing is needed. I just turned it off, it's applying the changes, we'll see what happens. Thanks for the tip! I'll let you know what happens!

Fred Wagner
frwagne@longbeach.gov

 

[FredWagner]

Turning off the Indexing service didn't harm the Kofax processes, but INETINFO.exe is still soaking up 99% of CPU cycles periodically. Next to decide whether a newer version of IIS would help, or adding a 2nd processor to the current server, or adding another server, and dividing the workstation load between the servers would be the best. I wish there were a forum for Kofax Ascent products here - it would be nice to share solutions with others using the same app.

Fred Wagner
frwagne@longbeach.gov

 

[zaznet]

Some process is still eating up 100% of the CPU. It's not likely a problem with INETINFO.EXE but a problem with the OS not reporting what is running inside INETINFO's working space.

A second server or CPU and you will still have one that's holding 100%. Most likely a second CPU would allow you to run other things, but won't do much to improve the load INETINFO is taking. Just that you'll have another CPU for OTHER processes to use, so there is more performance overall on the server. I just don't think this will improve your response time for the application.

Just be sure you get the same speed processor if you add one

Nathan aka: zaz (zaznet)
zaz@zaz.net

http://www.zaz.net/

 

[FredWagner]

Nathan - good analysis - maybe I don't even need a tool to see just what threads or processes are being executed by INETINFO.exe at any given time - in this setup, it should be only the Ascent Ricochet client, by Kofax. The strange thing is, it's either full on 99% CPU useage by Inetinfo.exe, or nothing at all. Doesn't matter if it's one station running Ricochet or 10 of them. Perhaps it's designed that way - will ping Kofax on it! Or could there be some rogue process, virus type, that's also running in Inetinfo ? Next to figure out how to check for that...

Fred Wagner
frwagne@longbeach.gov

 

[zaznet]

It could be that the Ricochet client isn't configured for optimal performance. Might have some options you can change there to improve this. It's certainly NOT your IIS that's at fault, but the add-on software you are using.

A second CPU won't "improve" IIS realy, since the INETINFO should not get any benefit from it. Since the rest of the system is at 0% most of the time, there is no real harm being done by IIS using 99% when in use. The problem is that it should respond faster on the hardware you have.

I've worked with the same kind of problem with Crystal Reporst. Oh was that fun. Our problem there was if it didn't complete in time and we had too many users in queue, we'd lock the application up because we ran out of licenses. In our situation performance was the difference of being up or down.

Some configuration chagnes were made to close out the users sessions earlier. IIS supports "keep alive" to keep the users session active even after the page has been sent to the user. We also upgraded our software.

Check with the vendor as you stated, they might have some tuning tips for you. We use RightFAX connected to Exchange 2000 and 2003 and it hardly ever peeks. I think those 4 servers are dual 1.4 Xeon.

Nathan aka: zaz (zaznet)
zaz@zaz.net

http://www.zaz.net/

 

[FredWagner]

Problem sovled! Rather than analyze it to death, after we're removed and reinstalled everything else related to it, we removed IIS itself from the server, then reinstalled it. THAT cured the problem. (IIS is a Windows Feature, so you have to use that option in Add/Remove programs) Getting IIS back on the server was a bit tricky - Win2K AS insisted on seeing a CD or folder with Windows2000AdvServer with SP3 (the current level of the server) integrated. After reinstalling IIS, we reinstalled the rest of the Kofax Ricochet system, and we're off and running properly.

Fred Wagner
frwagne@longbeach.gov

 

[zaznet]

Great,

Thanks for letting us know the final resolution.



Nathan aka: zaz (zaznet)
zaz@zaz.net

http://www.zaz.net/