[Neuro Toxin]

SRCDS for windows places networking on a seperate worker thread allowing another core to take the workload when the main server thread is using an entire core.

This means you might get a few extra client slots however: as networking moves to another core it could affect the performance of servers that end up sharing the same cores.

As a consequence, you may get higher slot servers but you wont be able to host one server per core as CPU variance will be less stable.

[Mikado]

Originally Posted by Neuro Toxin SRCDS for windows places networking on a seperate worker thread allowing another core to take the workload when the main server thread is using an entire core. This means you might get a few extra client slots however: as networking moves to another core it could affect the performance of servers that end up sharing the same cores. As a consequence, you may get higher slot servers but you wont be able to host one server per core as CPU variance will be less stable.

ahh thank's i got the windows part, on linux if you launch a server without the taskset it will use a random full phisical core or a random thread, since SRCDS can't use the multi-threading on linux, for ex if you have an 4 cores CPU with 8threads, can you run 8 servers per thread or 4 per core ?

[asdfxD]

Originally Posted by Mikado ahh thank's i got the windows part, on linux if you launch a server without the taskset it will use a random full phisical core or a random thread, since SRCDS can't use the multi-threading on linux, for ex if you have an 4 cores CPU with 8threads, can you run 8 servers per thread or 4 per core ?

for linux server use one physical core for 1 server with taskset. better performance and less cpu usage. var is spiking without taskset if you run multiple servers. some people say dont use taskset on srcds and let the os handle the load, the os knows it better... but you have better results when using taskset.

[Mikado]

Originally Posted by asdfxD for linux server use one physical core for 1 server with taskset. better performance and less cpu usage. var is spiking without taskset if you run multiple servers. some people say dont use taskset on srcds and let the os handle the load, the os knows it better... but you have better results when using taskset.

but if you let the os choose, it can set 2 servers on a single core ? ( that's bad actually, especially if you have multiple users )
and when you say using taskset and giving a phisical core, on the taskset parameter you need to give two threads ?

[Neuro Toxin]

Speaking my experience with Windows.

Using affinity results in a more stable var however: the point at which var starts going red and yellow is at a lower slot count meaning you cant host as many slots.

You also need to be carefull to not assign any SRCDS instances to virtual cores only. Hyperthreading means each physical core is split into two virtual cores. Assigning an SRCDS instance over two virtual cores which are on seperate physical cores will massively degrade performance.

Windows core scheduling is decent enough to ensure cores are not shared when SRCDS instances are using high loads.

[Mikado]

Originally Posted by Neuro Toxin You also need to be carefull to not assign any SRCDS instances to virtual cores only. Hyperthreading means each physical core is split into two virtual cores. Assigning an SRCDS instance over two virtual cores which are on seperate physical cores will massively degrade performance.

That's what i was talking about previously, if you let the os choose the srcds cores by itself it can set multiple server on a single core that will result in bad performances, and if you use taskset and you assign a SRCDS instance over two virtual cores which are on seperate physical cores it will result in the same bad performances.

So what's the best choice to follow ? for me i can't switch to windows because my host apply monthly fees for that.