[Puppetmaster]

Originally Posted by Major Erection So....in other words, it's not possible unless I get new hardware? What are threads and do they do for the servers?

In simple terms, a thread is an asynchronous data process which runs at the same time as the rest of the code. It usually allows something else to run concurrently along side the main server functions such as a background SQL query. In the case of sourcemod, in my experience this is generally some non time completion dependant data such as adding a kill to the database log (Anything that can be done out of order or of which the data does not need to be immediately accessed).

For 99% of users it does exactly nothing to have more threads currently but hopefully in the future more code can be threaded.

Edit: Sorry for convolution. Have not yet had coffee.

[cristi_ip]

Originally Posted by Taner High/realtime for linux: https://forums.alliedmods.net/showpo...64&postcount=8 For unlimited bandwidth you can try net_compresspackets 0

How do I set up in linux what you said in that post:
"chrt -f -p 40 `ps aux | grep srcds_linux | grep xxx.xxx.xxx.xxx | grep 270XX | awk {'print $2'}`"

Thank you!

[Taner]

Originally Posted by cristi_ip How do I set up in linux what you said in that post: "chrt -f -p 40 `ps aux | grep srcds_linux | grep xxx.xxx.xxx.xxx | grep 270XX | awk {'print $2'}`" Thank you!

Change xxx's to your ip and port. Test it you can check the chrt is right or not with "top"(PR). If all good add to root cron.

[cristi_ip]

Thanks for the reply Taner, can you tell if is ok as it now ?

[Taner]

Originally Posted by cristi_ip Thanks for the reply Taner, can you tell if is ok as it now ?

If i remember right PR must be show "40" not "-40".

[Major Erection]

Originally Posted by Puppetmaster In simple terms, a thread is an asynchronous data process which runs at the same time as the rest of the code. It usually allows something else to run concurrently along side the main server functions such as a background SQL query. In the case of sourcemod, in my experience this is generally some non time completion dependant data such as adding a kill to the database log (Anything that can be done out of order or of which the data does not need to be immediately accessed). For 99% of users it does exactly nothing to have more threads currently but hopefully in the future more code can be threaded. Edit: Sorry for convolution. Have not yet had coffee.

I know that it runs on the physical core not the threads but this is me running 4 full servers but the cpu only shows 42% load.

It's a 4 core 8 thread processor.

http://i.imgur.com/iEcYzp9.png

[Puppetmaster]

Originally Posted by Major Erection I know that it runs on the physical core not the threads but this is me running 4 full servers but the cpu only shows 42% load. It's a 4 core 8 thread processor. http://i.imgur.com/iEcYzp9.png

Take a little look in the top right corner at the LOAD. Load is the average of all the logical cores. Any load over 4 on a 4 physical core CPU in theory means 100% load. In practice people tend to use the rule of thumb of 0.7 load per physical core for smooth running.

From the image you have linked everything seems to be working fine. The server is under heavy load though.

[Puppetmaster]

Just found a source that happens to have used most of my wording too xD

http://blog.scoutapp.com/articles/20...-load-averages