Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

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

How do you limit a single process program run in a Windows environment to run only on a single CPU on a multi-core machine?

Is it the same between a windowed program and a command line program?


  • Reason for doing this: benchmarking various programming languages aspects
  • I need something that would work from the very start of the process, therefore @akseli's answer, although great for other cases, doesn't solve my case
share|improve this question
Why do you want to do this? Letting the OS decide which CPU/core runs which process it going to be much more efficient. – ChrisF Jul 12 '11 at 13:24
in order to benchmark various programming language aspects – Jonathan Jul 12 '11 at 14:00
That's a good reason - you should have included that information in your question. It's important. – ChrisF Jul 12 '11 at 14:08
Motivation isn't essential, but I added it following your advice – Jonathan Jul 12 '11 at 14:38
However, it might be the information someone needs to be able to provide an answer. – ChrisF Jul 12 '11 at 14:39

If you're running Windows Vista/7 (possibly XP, but not sure) it's really rather simple.

Type in: Control+Shift+Esc to get your taskmanager up.

Click on the Processes tab

Find the process that needs its processor affinity changed

Right-click on the process

Click on "Set Affinity"

Here you can select which processor(s) your process will use.

Good luck!

EDIT: You have to be administrator to get this to work.

share|improve this answer
Really nice, i didn't know that. Good answear +1 for me. – Diogo Jul 12 '11 at 13:26
An affinity is not a guarantee. The processes will prefer this processor, but if it has several threads they won't all stay there. – Joel Coehoorn Jul 12 '11 at 13:40
It's not a guarantee but it's a beginning. You can also maximise your probabily of getting the processor you've set the afinity for if you set logical affinities for your most processor-hungry tasks. – akseli Jul 12 '11 at 13:43
This is good, but I need something that will be deterministic right from the start – Jonathan Jul 12 '11 at 14:01
@JoelCoehoorn: No, it is a guarantee. What you're talking about is the preferred processor vector, which is different from the affinity vector. – Mehrdad Feb 18 '13 at 6:10

from the command line, use

start /affinity 1 program.exe

this will run program.exe on the first CPU as "1" is the hex value of the affinity mask

CPU3 CPU2 CPU1 CPU0  Bin  Hex
---- ---- ---- ----  ---  ---
OFF  OFF  OFF  ON  = 0001 = 1
OFF  OFF  ON   OFF = 0010 = 2
OFF  OFF  ON   ON  = 0011 = 3
OFF  ON   OFF  OFF = 0100 = 4
OFF  ON   OFF  ON  = 0101 = 5 
OFF  ON   ON   OFF = 0110 = 6
OFF  ON   ON   ON  = 0111 = 7
ON   OFF  OFF  OFF = 1000 = 8
ON   OFF  OFF  ON  = 1001 = 9
ON   OFF  ON   OFF = 1010 = A 
ON   OFF  ON   ON  = 1011 = B
ON   ON   OFF  OFF = 1100 = C
ON   ON   OFF  ON  = 1101 = D
ON   ON   ON   OFF = 1110 = E 
ON   ON   ON   ON  = 1111 = F 
share|improve this answer
Revolter: Do you know if I can do the same with Services initialization? – Diogo Jul 13 '11 at 11:51

Depends on what you are willing to do:

Method 1: On demand

Use ImageCFG. This utility will let you setup an executable to run on any number of cores. Make sure you backup your target executable before making the changes and restore it when you are done playing with it.

Method 2: Force an entire Windows Session (Vista/7)

  1. Type bcdedit /set onecpu on on a command prompt
  2. Reboot the system.
  3. When you are done playing, type 2 - Type: bcdedit /set onecpu off and reboot again.

Method 2: Force an entire Windows Session (XP)

  1. Open your boot.ini file (Right-click My Computer -> Properties -> Advanced Tab -> Settings button under 'Startup and Recovery' -> Edit button in 'System Startup').
  2. You'll find the following (or similar) section in the file:

    [operating systems]

    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

  3. Change it by adding the /onecpu flag:

    [operating systems]

    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /onecpu

  4. Reboot. Once you are done playing remove the flag and reboot again.

Method 0: Not a good method (Processor Affinity)

Anything that otherwise involves Processor Affinity isn't a good option, I'm afraid. Processor affinity is a clue to the processor. The processor is not obliged to respect it, and often will not.

share|improve this answer
Method 2 doens't seem to work on Win7. D:\>bcdedit /set onecpu results in The set command specified is not valid..... The parameter is incorrect. – max Oct 12 '12 at 6:19
you forgot 'on' – A Dwarf Oct 25 '12 at 23:19
Processor affinity is not a "clue to the processor". If anything, it would be a clue to the operating system scheduler. – Mehrdad Feb 18 '13 at 6:11
@Mehrdad: If I give you a "clue to the answer", that means the clue helps determine the answer, not that the answer uses the clue. – David Schwartz Feb 18 '13 at 21:33
"Prostitutes appeal to pope." "Two Soviet ships collide, one dies." – David Schwartz Feb 19 '13 at 0:04

I put the following function in my program in python 2.6 and it calls windows functions. My machine has only two cores so you may need to change that part. The comments tell you how to see what the current affinity is. It works "as is" for a single core machine if you set or default to a mask of 1.

def setaffinitymask(pid = None, mask = 1):
    """ Set The Affinity Mask of a Windows Process.  Affinity Mask is a value between 1-3 where
        1 is for core 0, 2 is for core 1, 3 is for both cores (it is a bitmap)
        Default sets the Affinity Mask to core 0 only
        python process can take any valid process ID. """

    import win32api, win32process, win32con

    if pid  == None:
        pid  = win32api.GetCurrentProcessId()
    if mask == None:
        mask = 1
    if mask  < 1 or mask > 3:
        mask = 1
        print 'process affinity mask out of range [1..3] setting it to 1'
    handle = win32api.OpenProcess(win32con.PROCESS_ALL_ACCESS, True, pid)
    # see what mask is currently set to
    # processAffinityMask, systemAffinityMask = win32process.GetProcessAffinityMask(handle)
    # print 'process affinity mask = ', processAffinityMask, ', system affinity mask = ', systemAffinityMask
    # set affinity for process to mask value
    win32process.SetProcessAffinityMask(handle, mask) # 1=core 0, 2=core 1, 3=both
    processAffinityMask, systemAffinityMask = win32process.GetProcessAffinityMask(handle)
    #print 'process affinity mask = ', processAffinityMask, ', system affinity mask = ', systemAffinityMask
share|improve this answer
Not sure if OP asked for a code... – bytebuster Dec 15 '12 at 22:59

In Windows 8, you have to go to the Details tab of the task manager to do Set Affinity. It doesn't give you the option on the Processes tab.

EDIT: Also, if the program you want to start has parameters, this thread could come in handy: How to start a program with command line arguments on Windows' cmd with 'start' command?

share|improve this answer

As I went looking for very similar information using PowerShell, I found the information I needed here:

You didn't mention which Windows OS you were using, (The older ones didn't come with PowerShell, although you could install it if it's not there).

The quick of it, is that in PowerShell, process affinity is simply a property you can change easily.

To see the properties (and other tidbits of info) of your process (using foo as an example process), the PowerShell command would be:

Get-Process foo | Get-Member

You'll see ProcessorAffinity is one of those properties. Changing it is trivial, and you can select which core you want to run on, using the values from Revolter's table/link above.

To see what the value of the ProcessorAffinity property is for foo, here's the command:

(Get-Process foo).ProcessorAffinity

So if you wanted to run foo on cpu 4 only, you would set the value as such:

(Get-Process foo).ProcessorAffinity=8

share|improve this answer
I can’t tell from your explanation: does this apply only to existing processes? The OP doesn’t want to start a process and then set its affinity; he wants to start a process with its affinity already set, as in the start /affinity answer. Can your technique do that? If so, please explain how. – Scott Jul 23 '13 at 23:33
@Scott Existing processes only. In the context you provide, my answer doesn't help. I felt that the "very start of the process", was a matter of starting the process & then immediately setting its affinity. I.E.: Start-Process foo ; (Get-Process foo).ProcessorAffinity=8 However, after reading your comment, and finding that Start-Process has a missing affinity flag itself, I came up with the following, which I tested: [System.Diagnostics.Process]::start("foo.exe").ProcessorAffinity=0x0010 – Bewc Aug 26 '13 at 21:00
I suggest that you edit your answer to add that alternative. – Scott Aug 27 '13 at 22:36

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .