SRCDS Steam group


hlds (cstrike) unstable fps
#16
did you try 2.6.28 with or without rt paches? I recently switched to 2.6.31-rc4-rt1, it seems to run smooth (though it is not yet a stable kernel release!), maybe you can try that as well...

make sure if you chrt that you also give the timer interrupt processes (sirq-hrtimer etc.) the correct priorities, as described in the howto.

also try all pingboost settings, pb3 is not always the best. those are simply different techniques, there is no hierarchy. I also recommend a higher sys_ticrate like 2500, but you should also try this out.

don't look too much at the cpu usage. unless you see real problems (like fps drops or slow system performance) you can ignore high cpu usage as this might very well be fake. btw: how to you measure cpu usage?
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
#17
BehaartesEtwas Wrote:did you try 2.6.28 with or without rt paches? I recently switched to 2.6.31-rc4-rt1, it seems to run smooth (though it is not yet a stable kernel release!), maybe you can try that as well...

make sure if you chrt that you also give the timer interrupt processes (sirq-hrtimer etc.) the correct priorities, as described in the howto.

also try all pingboost settings, pb3 is not always the best. those are simply different techniques, there is no hierarchy. I also recommend a higher sys_ticrate like 2500, but you should also try this out.

don't look too much at the cpu usage. unless you see real problems (like fps drops or slow system performance) you can ignore high cpu usage as this might very well be fake. btw: how to you measure cpu usage?

BehaartesEtwas, thank you for the reply! Is there a 2.6.28? I'm running 2.6.28.1 as that is the lowest i can find on kernel.org. I am running 2.6.28.1 without the RT patch (i dont see any RT patches for the 6.28 series kernel here: http://kernel.org/pub/linux/kernel/projects/rt/older/), with low latency desktop priority. This combo seems to produce completely stable fps with chrt, but unfortunately the cpu load being reported by htop seems real, cpu temperatures raise by over 10c with 4 servers idling, and if i run more than 1 server per core, even idling servers, the whole machine is slow to respond and FPS are stuck in the 60's. Also, i am running your resched.sh script to set the priority on everything, and as stated in a previous post while that achieves perfect fps with my current configuration the cpu usage is just too high to live with.
Reply
#18
well I don't have much experience with vanilla kernel, usually they didn't work well for me....
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
#19
any sys_ticrate setting over 1005 produces a noticeable speed up in gametime with a vanilla kernel.
[Image: b_350x20_C002748-004880-FFFFFF-000000.png]
Reply
#20
pengy Wrote:any sys_ticrate setting over 1005 produces a noticeable speed up in gametime with a vanilla kernel.

not on all systems. you have to try it out... and in any case this is only true for pingboost 3, if I am not mistaken. so pb2 and sys_ticrate 2500 can be better than pb3 and sys_ticrate 1005...
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
#21
Really? I gotta try this out...
[Image: b_350x20_C002748-004880-FFFFFF-000000.png]
Reply
#22
So BehaartesEtwas, have you experienced the issues with pingboost 3, screen and chrt in regards to incredibly high cpu usage? I've been trying different combination's for days now and so far the only one that gives stable fps is pingboost 3, sys_ticrate 1000+, and chrt. But obviously i need to run all of this in a screen which makes it all useless with the amount of cpu usage it is requiring. Thanks!
Reply
#23
no sorry, I had never any differences running servers inside a screen or not. maybe you should have a look at your screenrc config file, there could be something wrong...
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
#24
BehaartesEtwas Wrote:no sorry, I had never any differences running servers inside a screen or not. maybe you should have a look at your screenrc config file, there could be something wrong...

I'm just using the stock screenrc that comes with debian lenny, i have pasted the contents here: http://pastebin.com/m3aa763fd Are you using something different? Would you mind pastebin'ing it? Thanks.
Reply
#25
hm, can't find anything unusual there... mine is the stock of gentoo: http://pastebin.com/m7ece69d6
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
#26
BehaartesEtwas Wrote:hm, can't find anything unusual there... mine is the stock of gentoo: http://pastebin.com/m7ece69d6

Hrmm, well as expected copying that didn't help, thanks for posting it anyways. Can i ask what kernel you are running that is able to produce the stable 1.6 fps without the crazy cpu usage bug? Running the 2.6.26.8-rt16 exactly as in your guide the CPU usage is normal, even with chrt, but fps are wildly unstable no matter what i try. Switching to 2.6.28 or 2.6.28.1 with modifications from your guide, minus an RT patch produces perfectly stable fps but with insanely high cpu usage.
Reply
#27
I didn't have that problem running 2.6.28.8-rt16, but now I use 2.6.31-rc4-rt1 (pay attention, that's still a release candidate)
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
#28
BehaartesEtwas Wrote:I didn't have that problem running 2.6.28.8-rt16, but now I use 2.6.31-rc4-rt1 (pay attention, that's still a release candidate)

Yeah i had already tried that kernel but failed to mention it in my post, sorry about that.
Reply
#29
The kernels aren't the problem. It's probably some BIOS errata, or something else.
http://leaf.dragonflybsd.org/~gary

“The two most common elements in the universe are hydrogen and stupidity.”








Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)