Yeah, that's true. We should try to write our official Plutonium tutorial for Linux. As I mentioned, I only reference this guide and the other one in this forum section when I forget how to export wine arch for example.
Pretty sure in the end I only run 10% of the commands in this tutorial 🤣.
Considering the server (game) only has two relevant logical threads: the main thread and the game thread, it still doesn't make much sense to me. If the system isn't busy it should quite never switch a process between cores. Even so, then why you are giving the game more cores if you intend to stop that behaviour?
The OP said it is to improve the performance which I am doubtful of, and you say it's for stopping a behaviour that's contradictory to giving the game more cores. But correct me if I misunderstood the comment.
Edit:
I did some Googling, it seems in the context of IW5 it's somewhat desirable to have both the main thread and the game thread running on the same physical core. So it is my opinion that the step should be skipped entirely as well. Since the main thread and game thread will be interchanging data often if they are on the same core the threads can take advantage of cache hits and so forth. Then again, without profiling the game, it's not possible to give credit to OP's theory the game will benefit from more cores. The game isn't designed for multithreading because as mentioned before a dedicated server has only two important threads.
On IW5 I think we only have one logical thread that does the work on the main and game thread.
It's a patch NTA did on IW4 devices to improve performance.
