Welcome to weblogs.com.pk Sign in | Join | Help


We have a mediocre server in production where usually the scheduled job executor kind of apps get deployed...The machine is also running one Windows Service, coded in C#/.Net, developed by me. My system administrator ranged me saying that i should get it checked as machine' CPU is hitting high most of the time. Debugging (Windows) applications in production is tricky, and will need separate discussion...(and many developers and sysadmins dont have enough knowledge and know-how about getting it done in the right way). Anyways, I suggested him to use SysInternals Process Explorer (Microsoft bought SysInternals), very handy tool...and he reported back that ACE****.exe process is culprit...(which is very old third party app and it has been running fine for ages). I guessed (not yet confirmed) that due to some OS patch (or something) it has started behaving so..

I went ahead and installed ThreadMaster, an application based CPU Quota management tool...its free....runs as Windows Service and has very simple registry based settings through which you can limit CPU per application...


I restricted ACE****.exe to 30%, and machine started behaving just fine...

Published Thursday, September 25, 2008 2:19 AM by khurram


# re: ThreadMaster

Monday, October 13, 2008 9:24 PM by jahil

If you are using Windows Vista; replace ThreadMaster with THREADORDER ..... Why the heck they are changing hive names :)

New Comments to this post are disabled