Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Windows Service that simply listens for certain events. Once triggered, the service executes a process (.exe).

My problem: On windows server 2003, this works great. CPU for the executable goes up to about 20% and it works at a reasonable speed.

On windows server 2008, it works 3 times slower (at least) and the CPU for the executable is about 1% if done the same way. However, simply running the executable (without the listening service doing it), it works just as fast as it does normally on windows server 2003.

This seems to be a problem with Windows Server 2008 not giving the same priority to the executable, yet nothing different can be seen on the Task Manager (other than CPU usage). It may also be something else altogether.

Any ideas what could solve this irritating problem?

share|improve this question

migrated from Jan 11 '10 at 17:09

This question came from our site for professional and enthusiast programmers.

Sounds like a configuration issue on 2008, which will get better answers over on – Will Jan 11 '10 at 16:51

have you explicitly specified the priority of the process when you dispatch to create a new process CreateProcess() - parameter dwCreationFlags -- if NORMAL_PRIORITY_CLASS (default) is specified it inherits from the parent process ?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.