SRCDS Steam group


serverwide world freezes 1-2 seconds, RT/CHRT related?
#1
Hello everyone, i have only observed this on TF2, but i believe it is happening server wide regardless of game. Started with 2.6.26.8-rt16, everything setup as the wiki states, about once an hour the server will freeze/pause for a second or two. Tried again with stock 2.6.26.8, no RT patch, same issue. Tried tickless, 100HZ, no RT patch, same issue. Could this possibly be related to chrt being fired off every 5 minutes by cron? Do i need to set the priority of some other process to a higher priority than srcds? I tried setting the hrtimers, and sirq-net's to higher priority when i was running the RT patch, no improvement there. This is happening on debian lenny, 2x E5420's, 8gb fb-dram, 100mbit, less than 1 game server per core running. As of now i am back to using a stock kernel without chrt to see if this continues to happen. Thanks for any input.
Reply
#2
I was getting similar results every time i put that rt patch on.

I have had the best luck with a vanilla, 1000hz, no hi-res timer support. Gets 500fps, pretty stable.

that hi-res timer support i think is what kills me, every time I enable that, I get horrid performance in-game... even though rcon stats will show stable 1000fps.
Reply
#3
Thanks for the reply BrutalGoerge, does that mean hrtimer support unchecked completely in menuconfig, or just no RT patch? Right now i have hrtimer support checked, but i dont have the RT patch applied. Also, are you chrt'ing your servers to a higher priority to achieve fps stability, or just leaving it all stock?
Reply
#4
have you also raised the sirq-hrtimer threads in priority with chrt? else your game servers have a higher priority then the timer they depend on -> very bad
http://www.fpsmeter.org
http://wiki.fragaholics.de/index.php/EN:Linux_Optimization_Guide (Linux Kernel HOWTO!)
Do not ask technical questions via PM!
Reply
#5
BehaartesEtwas Wrote:have you also raised the sirq-hrtimer threads in priority with chrt? else your game servers have a higher priority then the timer they depend on -> very bad

Thanks for the reply BehaartesEtwas, yes i have done that and it made no difference.
Reply
#6
maybe try just a vanilla 2.6.29, on my box that was close to 2.6.26.8-rt11.
http://www.fpsmeter.org
http://wiki.fragaholics.de/index.php/EN:Linux_Optimization_Guide (Linux Kernel HOWTO!)
Do not ask technical questions via PM!
Reply
#7
BehaartesEtwas Wrote:maybe try just a vanilla 2.6.29, on my box that was close to 2.6.26.8-rt11.

Thanks for the reply BehaartesEtwas, when you say vanilla, do you mean just tickless, 100HZ, disable hrtimer support?
Reply
#8
vanilla means no patches. use the same configuration as described in my howto (apart from the realtime options which will just not be there). I don't know if this will be better, but it is worth a try...
http://www.fpsmeter.org
http://wiki.fragaholics.de/index.php/EN:Linux_Optimization_Guide (Linux Kernel HOWTO!)
Do not ask technical questions via PM!
Reply
#9
Thanks again for your help, do you still recommend running the resched.sh cron omitting the hrtimer line to set higher priority?
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)