We use multiple colo facilities and I personally have mastered the methods and tools for verifying the quality/capability of them. Contact me offlist and we'll be happy to add your colo to our monitoring that you'll be able to view firsthand via web graphing the answers you seek. Could mean the difference between losing a good provider or being stuck with a bad one.
Ray -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of doomed999 Sent: Thursday, November 10, 2005 8:25 PM To: [email protected] Subject: RE: [hlds_linux] Wierd Choke Problem > Set this to maximum inbound pipe speed, in bytes per second. There may be caps on server rate variables, but not here. Not understanding what you mean.... > Cl_updaterate 66 > Cl_cmdrate 66 Tried those, same outcome... > Thus the 66 suggestion. This should minimise choke readings, even the detail in net_channels. I also have to worry about the clients :) One pointed it out to me because he uses cl_up and cmd at 100 fine on other servers yet choke upto 25 in ours... > This is more than capable. That's whats making me wonder if it's a network issue...Any way to check? > Check the server side FPS too, using rcon stats. Source running at 160's HLDS running multiple, tryied on stocks (mid 80's) 150's, 300's upto the 900's for giggles... Thinking about maybe a new colo on other backbones, but I am lost... _______________________________________________ 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
