On 12/01/2009 03:47 PM, Gary Stanley wrote: > SCHED_RR gives the same latency as SCHED_FIFO, in my tests. Under > load, this will be different, though. (send me a message and i'll > send you some code) > I use a multicore system with one core 'dedicated' to each instance. In this case, FIFO basically gives that core to the process - it gets to use it before anything else can think about being scheduled. SCHED_RR would be very similar in this case, if not identical on one process-per-core. RR might make more sense if two or more srcds's are sharing the core.
>> Miscellaneous nonsense: >> - On a system with hi res timers and TSC/HPET, sleep() will return >> independent of the interrupt timer, enabling 1000FPS to be hit >> regardless of system ticrate. In this case, a 1000hz interrupt timer >> will not have any effect, and possibly a negative one. > > AFAIK select()/poll() on older kernels do not use hrtimers at all. > Only nanosleep()/usleep() do. You don't need 1000hz anyways as that > can cause cacheline pingpongs etc (Hurt NUMA performance) Indeed, this is all relevant to modern kernels. With older kernels, YMMV. >> - On linux/tf2, the stats command calculates fps in a very useless >> manner. A single slow frame will make it show '40fps', while the >> engine's own internal counter (what you see in the green banner in those >> windows srcds windows) as well as host_profile disagree. >> - fpsmeter.org uses the stats command. >> - I've talked to and worked with many people and never seen a linux TF2 >> server above 20 slots get 'stable' FPS, much less according to fpsmeter. >> I've seen many TF2 linux servers that perform very well and lag free. >> - RT kernels chug CPU like no tomorrow for very little benefit, vs FIFO >> scheduling and hi-res timers. >> - If your var is<10ms and your updaterate is stable 66, to hell with >> anyone whining about FPS (flamewar lol). Its worth noting that windows >> servers are tuned to run at 66fps originally. By valve. The 'booster' >> came later. >> - My linux TF2 servers are among the best stability in updaterate and >> var i've seen anywhere, yet many people have 'more stable FPS' than me. >> See previous point. >> - SourceTV is a massive buggy resource hog. >> - Anyone that brings up 'hit registration' probably doesn't know wtf >> they're talking about and read some old article about it with >> questionable logic. > > As long as you run Low Latency in the kernel with little interrupt > behavior, and without CPUspeed/ACPI Processor you should be > okay. Realtime kernels chug too much cpu because the scheduler has > more overhead etc etc > - > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
