Cpu usage/affinity on future GP releases

Dear development team.

Something came to my mind about new upcoming cpus and software release of GP

I remember there was some topics about the new intel hybrid cpus (Performance and efficiency cores) about disabling the efficiency cores to improve the real time audio. As audio is usually a single core process, i wonder if the current or new GP releases can select a high performance core. And i am interested on this topic because AMD will follow intel pattern and will go with hybrid architecture.

I am not an expert of these kind of topics but i know we can select in what core GP can run either with task manager or the sw called cpu lasso.

Could you clarify how is this managed?

Thank you

1 Like

If you are on windows, then you can create a shortcut to open gigperfomer with any processor affinity you want - no need for process lassoo

Instructions are for win 8, but is the same for later versions

More in brief:

https://answers.microsoft.com/en-us/windows/forum/all/how-to-permanently-set-priority-affinity-with/4e83fd39-34a7-49fe-a54a-ee891c38b737

2 Likes

This Is a very useful article. Thanks

Hmm, so you could set it up so GP always runs on performance cores? (and different instances of GP run on different performance cores)?

Yes, you could exclude any efficiency cores so GP always ran on performance cores

Also possible to set different instances of GP on run on different Performance cores.

Prob worth checking with the devs if this is the right thing to do: I recall some VST can use multiple cores, so not sure what happens with these when running within GP.

I’ve never been convinced that SetAffinity is a good idea for most purposes.

For a start, while setting the affinity of a process to a single core guarantees that the process will run on that core, it doesn’t prevent other processes from running on that same core. So you’d have to go and set the affinity of all the other processes so they only use other cores. And processes come and go.

In general you’re far better off letting the OS decide the affinity of a process.

Maybe just exclude all non-performance cores?