What does the "in" value mean?

[JayHax0r]

When you type net_graph 3 in console and look at the bottom right. You see something that says 'in:'



In that screen shot, on my server, the 'in:' value fluctuates a lot and jumps to as high as 2000 at times and I believe that it has to do with the lag on my server. Anyway to fix this?

[realchamp]

It's the amount of traffic send to you by the server.

It may become more smooth if your server ran with a higher sv_maxrate

[BehaartesEtwas]

actually, you have set on client side an updaterate of 20, so you might want to increase that. the server already forces you to a higher rate, that's why there it is 37, not 20 (most important are the last numbers! the client-side set-points are above/below the respective real value)

[JayHax0r]

So is there anything I need to do server side? I'm noticing not only mine, but my friends choke going from 0 to 50. Fluctuating constantly. What's wrong?

[BehaartesEtwas]

can you post the current net settings of your server?

and maybe this helps you also:
http://wiki.fragaholics.de/index.php/EN:Source_Netsettings#Server_Side

[JayHax0r]

Well, I'm currently collocating my machine with these guys.

http://www.continuumdatacenters.com/index.html

// rates
sv_maxupdaterate 67
sv_minupdaterate 30
sv_maxcmdrate 67
sv_mincmdrate 30
sv_maxrate 100000
sv_minrate 10000

[realchamp]

(03-06-2011, 03:21 AM)JayHax0r Wrote:  // rates
sv_maxupdaterate 67
sv_minupdaterate 30
sv_maxcmdrate 67
sv_mincmdrate 30
sv_maxrate 100000
sv_minrate 10000

Your rates are good, no problem here.

I think the problem is the hardware. Since the server fps is 37 on that screenshot. And that's bad!

[coach]

Lower your maxrate. Try 20000 to start.

[realchamp]

(03-06-2011, 10:58 AM)coach Wrote:  Lower your maxrate. Try 20000 to start.

That will cause massive chockes, which would decrease server performance.
Better to set it at 30000.

[BehaartesEtwas]

if the effective client rate (i.e. after clamping client-side rate to whatever sv_minrate and sv_maxrate are) is lower than needed to maintain the desired update/cmdrates, you get choke. so, if you have choke you have to rise client-side rate and maybe sv_maxrate. lowering helps only, if your rate exceedes what your connection can handle and you high ping or loss. but lowering cmdrate and updaterate in that case is much preferrable...

with your server netsettings, people can create choke by using cl_cmdrate and cl_updaterate of 66 but having rate on 10000. so make sure you don't use those kind of (incorrect) client netsettigs.

also, as realchamp stated, your server fps might be the problem. if you are unsure, you can use fpsmeter.org to check this (post the link here). your server fps should stay always above 66, else it will not maintain a stable updaterate. that does not explain choke though (but probably lags!)...