Right, but the change in CPU load is probably trivial. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andreas Grimm Sent: Tuesday, February 24, 2009 3:19 AM To: 'Half-Life dedicated Linux server mailing list' Subject: Re: [hlds_linux] net_splitpacket_maxrate
Did I understand it correct? High net_splitpacket_maxrate: - High CPU load - Less lags, cos packets are compressed Low net_splitpacket_maxrate: - Low CPU load - More lags, cos bytes are sent uncompressed :-O -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tony Paloma Sent: Tuesday, February 24, 2009 11:54 AM To: 'Half-Life dedicated Linux server mailing list' Subject: Re: [hlds_linux] net_splitpacket_maxrate I didn't notice how much CPU it adds. I imagine under normal gameplay that it's minimal. Don't set it to 66, that'd be a terrible idea. The value is in bytes/sec and defaults to 15000. You don't want to set it lower. In the pictures, I was setting it to 300000. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of JäKë T Sent: Tuesday, February 24, 2009 2:50 AM To: [email protected] Subject: Re: [hlds_linux] net_splitpacket_maxrate Have you noticed how much more cpu this uses up? net_splitpacket_maxrate 66 Going to test this out right now myself. Pictures look good, hope this works out nice. :) Thanks Tony. > From: [email protected] > To: [email protected]; [email protected] > Date: Tue, 24 Feb 2009 02:37:06 -0800 > Subject: [hlds_linux] net_splitpacket_maxrate > > 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 _________________________________________________________________ How fun is this? IMing with Windows Live Messenger just got better. http://www.microsoft.com/windows/windowslive/products/messenger.aspx _______________________________________________ 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 _______________________________________________ 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
