If you have a sys_ticrate above the HZ you're running at you'll run into issues. Simply put HZ 1000 slows the clock interrupts to 1000/sec and that's pretty much what sys_ticrate tells the HL server. I have my sys_ticrate set to 1000 matching the limit that the kernel is set to. I've noticed also that higher sys_ticrates also use more CPU so it's really a balance. I used to run at 500 but after nicing the process I kicked it up a notch and noticed ping/latency improvements across the board.
monkey13 www.hostage-down.net -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kenny @ Emsco Sent: Friday, May 07, 2004 6:58 AM To: [EMAIL PROTECTED] Subject: RE: [hlds_linux] Chokes... After testing last night choke was a lot lower with nice -19 and device polling. On standard maps 0 choke on custom maps 5-10 choke never above, and mostly 0 choke except for first 5 seconds of round start. All other settings stayed the same HZ 1000 Sys_tcrate 200 Maxrate 9999 Minrate 6500 Maxupdaterate 60 Minupdaterate 30 I have noticed some other servers showing sys_ticrate cvar and on some its set to 10,000 but they seem to run fine with 20-22 players. What benefit would you get from having it so high?? Kenny _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
