I was experimenting with net_splitpacket_maxrate and it seems it has a
definite noticeable effect. Assuming your server's CPU can handle the extra
load required by splitting an extra amount of large packets and compressing
this, I would recommend setting this to the same as your sv_maxrate (unless
your maxrate is zero, in which case you should set it to a real high value).
Look at these pictures:
http://www.sourceop.com/randomimages/net_splitpacket_maxrate/

Because of the constant stream of large amounts of incoming data, every
packet in the screenshots is part of a fragmented set. The CVar limits the
rate of these packets specifically and defaults to only 15000. This is a
problem because when there is large amounts of action, it is common for
update packets to be split because of their large size. If most of the
update packets need to be split, your rate will suddenly be dropped to
around 15,000.

I see no drawback to increasing the value of this CVar other than the
increased CPU load your server might get since it will be splitting and
compressing more outgoing packets.

Hope this helps,
Tony


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to