>Choke is simply an indicator that they're not getting as many world >updates as they'd like, either because your server can't or is >configured not to and/or because their system or network connection >can't handle it. Just because someone has a high choke number doesn't >mean that something's broken or not running right. It's not like loss >percentage.
Actually according to valve, it's not them getting a lack of updates that they want. Instead it's the server trying to send MORE updates then the client can handle. ---------- Choke happens when the server would like to send data to a client but it cannot because the client is not yet ready for more data (based on the client's "rate" setting or the server's sv_maxrate). Some things are obvious causes for choke, such as the client's rate simply being too low for the number of players on a server. Other things might not be so obvious, such as a client raising their cl_updaterate value too high. On a similar note, LAN server ops might not be aware of this, but for LAN servers (sv_lan = 1), client "rate" settings (and sv_min/maxrate) are totally ignored and 9999 is used for the rate of all clients. This will be increased to the max allowed rate, 20000, in the next major release, but it's something to keep in mind for now. By Leon Hartwig - VALVe ------------ _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
