> The best that seems to work is > rate 30000 Set this to maximum inbound pipe speed, in bytes per second. There may be caps on server rate variables, but not here.
> cl_update 50 Cl_updaterate 66 > cl_cmd 50 Cl_cmdrate 66 > But there should be no reason I can't run 100 in my eyes. It > normally spikes the worst when the bomb goes off and when the > round restarts. With source it seems worse spiking up to the > 30's with the 50 update rate. Server is running at 66 Tick. Thus the 66 suggestion. This should minimise choke readings, even the detail in net_channels. > HLDS running at default and same thing. It is doing with with > as little as one server on a machine. The machine specs are as follows > > Dual Xeon 3.0 2M cache > 2G DDR2 533 ECC > Running CentOS 4.1 > Fully Burstable 100Mbps Port (Possible problem?) This is more than capable. > The only thing I can figure at this point is an overloaded > network at the datacenter I am colocating through? I am at a > complete loss. Please give your input. Check the server side FPS too, using rcon stats. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
