*lol* 15 choke is nix ... ansonsten einfach netsettings runterschrauben ....

das meint valve zu thema choke :

Tell them to set the following vers

rate 25000
cl_cmdrate 101
cl_udaterate 30

That rate is way higher then most servers will allow but it wont hurt them
to have it that high. It will only let them use the max thats there.

The updaterate is the key. Tell them to start at updaterate at 20-30. Thell
them to move it up till they start to choke and then use the last setting
before that that they didnt choke at. If they choke with it at 20 they got
ISP/Bandwidth/Hardware issues.

und das :


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