I concur. Forcing too low rate, cl_cmdrate or cl_updaterate to client will cause choke effect.. It is best just not to force any maximum rate, unless its way more than tickrate of the server.
-ics Kevin Ottalini kirjoitti: > You can't just change sv_maxrate on the server and have it immediately > affect clients, the client must reconnect or reset his own rate for the new > setting to take effect. > > Many of us have thoroughly tested this and there is no question that having > a low sv_maxrate will cause / aggravate choke. > > Client's can have choke independently of the server caused by their graphics > card or system or internet. > If your client has choke on most servers then suspect your client not the > server. > > > > ----- Original Message ----- > From: "Saint K." > To: "'Half-Life dedicated Linux server mailing list'" > <[email protected]> > Sent: Wednesday, July 16, 2008 9:05 AM > Subject: Re: [hlds_linux] Choke Problem > > > >> Hi, >> >> At first I thought aswell that the rates were the issue, but I've tested >> (and just re-tested) it with a sv_maxrate of 30000, and a client rate set >> at >> 30000, but it will still give the exact same levels of choke. >> >> Cheers, >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Kevin >> Ottalini >> Sent: Wednesday, July 16, 2008 5:37 PM >> To: Half-Life dedicated Linux server mailing list >> Subject: Re: [hlds_linux] Choke Problem >> >> SpecialK, >> You have a limit set on rate that is causing this choke, I dropped into >> one of your servers and this is what I saw: >> >> "rate" = "15000" ( def. "10000" ) >> ** NOTE: The real value is 30000.000 but the server has temporarily >> restricted it to 15000.000 ** >> >> 15000 is way too low to support the number of players and events going on, >> the server is unable to get the updates in/out to clients (thus choke). >> >> For Source servers with more then 8 or 10 players I've found that a good >> low >> >> choke server requires at least sv_maxrate 30000 (and you might need even >> more with 32-player TF2 servers). >> >> qUiCkSiLvEr >> >> >> >> >> ----- Original Message ----- >> From: "Saint K." >> To: "'Half-Life dedicated Linux server mailing list'" >> <[email protected]> >> Sent: Wednesday, July 16, 2008 6:56 AM >> Subject: [hlds_linux] Choke Problem >> >> >> >>> Hi, >>> >>> We're currently experiencing a massive choke problem, and I can't seem to >>> find the issue. >>> >>> Here is a screenshot of the net_grap 3 running; >>> http://www.specialattack.net/downloads/choke.jpg >>> >>> All clients are experiencing these issues. >>> >>> We're having the choke issue's on both machines. One machine runs Debian >>> Etch with a tickles kernel(2.2.23), and the other machine runs also >>> Debian >>> Etch, but with a 1000Hz/preemt kernel (2.2.26). >>> >>> Both the TF2 servers run around 500FPS. The CPU load on the core is >>> around >>> 60-70% tops. >>> >>> I've tried various rate settings, but the choke seems to be a near >>> constant, >>> even with a low amount of players. >>> >>> The server is connected on a 100Mbit uplink, which is without problems as >>> far as we can see on the monitoring and other testing we performed. No >>> latency spikes, packet loss etc etc. >>> >>> Does anyone have any tips were I should be looking to solve this choke >>> problem? >>> >>> Cheers, >>> > > > _______________________________________________ > 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
