05-22-2009, 12:07 AM
fps_max 300
you don't need to select your target fps somehow in the kernel or system. hrtimers are timers that can fire at arbitrary frequencies and are not bound to any ticks in the kernel. unlike with the old "timer wheel" in the kernel, hrtimers need no intrinsic overhead to allow high timer frequencies, meaning if you are able to produce 1000fps with your system but limit the server to 300, you will only have the overhead of 300fps.
but beware that hlds/srcds always waits a multiple of 1ms after each frame, so you can only achieve certain fps values like 1000, 500, 333, 250, 200, ... (or values slightly below those "magic numbers").
you don't need to select your target fps somehow in the kernel or system. hrtimers are timers that can fire at arbitrary frequencies and are not bound to any ticks in the kernel. unlike with the old "timer wheel" in the kernel, hrtimers need no intrinsic overhead to allow high timer frequencies, meaning if you are able to produce 1000fps with your system but limit the server to 300, you will only have the overhead of 300fps.
but beware that hlds/srcds always waits a multiple of 1ms after each frame, so you can only achieve certain fps values like 1000, 500, 333, 250, 200, ... (or values slightly below those "magic numbers").
http://www.fpsmeter.org
http://wiki.fragaholics.de/index.php/EN:Linux_Optimization_Guide (Linux Kernel HOWTO!)
Do not ask technical questions via PM!
http://wiki.fragaholics.de/index.php/EN:Linux_Optimization_Guide (Linux Kernel HOWTO!)
Do not ask technical questions via PM!