How to isolate the core in multicore

[rajiraji12]

how to move os activity to one core & make isolation for remaining core

 

[HEXiT]

open task manager and select the application you want to run on 1 or more cores. right click on it and select set affinity... you will now have the choice of choosing 1 or more cores on which to run the program.

 

[rajiraji12]

open task manager and select the application you want to run on 1 or more cores. right click on it and select set affinity... you will now have the choice of choosing 1 or more cores on which to run the program.

I need to move all os activity to one core, remaining core to be kept isolated, how it can do?

 

[13thmonkey]

why do you need to do this?

 

[gamerk316]

Don't think you can. The scheduler is going to put things on whatever core it wants. You can disable a core entiely, but then you are limited to just one.

 

[silverliquicity]

Buy a single core CPU

 

[13thmonkey]

If you think it will 'free up the other cores so that they work quicker' then you are wrong, the scheduler is very complex, very good and works at making things run as quick as they can, it understands the dependencies. Putting all OS apps on one core would make things worse.

 

[truegenius]

you can not change core assign of all processes, some will refuse to do that
you can try task manager, process manager of tuneup, task assignment manager (google it up)

 

[rajiraji12]

Don't think you can. The scheduler is going to put things on whatever core it wants. You can disable a core entiely, but then you are limited to just one.

is to possible to run the specific application in the isolate core in order to improve application performance

 

[13thmonkey]

why do you think this will improve performance?

you would have to both lock an application to a core, and lock ALL other applications to the other cores. This would probably decrease performance.

What program, and what are you experiencing as symptoms, system specs too please.

 

[gamerk316]

Here's an example why the OS is smarter then you are:

Back in the dark ages, most programming languages had the "register" attribute, which would tell the compiler to keep a specific variable in a register whenever possible. This was supposedly an optimization, because some often-read data would increase performance if it never had to be read from main memory. [Remember, this was before large CPU caches existed].

In every case I can think off, use of this attribute tanked performance, because frankly, the optimizing compiler was smarter then the guys writing the software in the first place when it came to optimizing code.

Same logic applies here. The scheduler is going to use the core that makes the most sense when assigning a core to a thread. And the OS will run a thread when its priority/wait time dictates it should be run.