I don't know about your particular situation, but for the money you paid
for this "server class" CPU and the motherboard, you could have gotten
much better performance out of a desktop CPU and board. You probably
should have gone with a CPU with fewer cores but a higher clock frequency.
There are very few tools in the srcds process itself that will help you
troubleshoot issues outside of memory exhaustion and configuration
problems, so don't look there.
You need to be using "net_graph 5" on the client. What is your app ping
like? When you get over 80ms, you will start to see a choke effect that
is very similar to TCP window exhaustion. It seems to be built into the
server, where if it does not get client feedback in time, it will choke
off future updates. As far as I know, there is nothing that can be done
about this.
Do yourself a favor and do this;
On my Windows 7 system, the path of my TF2 cfg directory is this;
C:\Program Files (x86)\Steam\SteamApps\<username>\team fortress 2\tf\cfg
In this directory, create or edit the file named "autoexec.cfg"
Put the following into the file;
Code:
//netgraph script
alias graph "graph1"
alias graph1 "net_graphpos 1 ; net_graphproportionalfont 0 ; net_graph 4
; alias graph graph2"
alias graph2 "net_graphpos 1 ; net_graphproportionalfont 1 ; net_graph 4
; alias graph graph3"
alias graph3 "net_graphpos 1 ; net_graphproportionalfont 0 ; net_graph 1
; alias graph graph4"
alias graph4 "net_graphpos 1 ; net_graphproportionalfont 1 ; net_graph 1
; alias graph graph5"
alias graph5 "net_graphpos 1 ; net_graph 0 ; alias graph graph1"
bind "p" "graph"
This script makes it so that when you press "p" on your keyboard, it
cycles through the net_graph in four different styles;
graph plus large-text stats
graph plus small-text stats
large-text stats with no graph
small-text stats with no graph
On the netgraph, pay attention to the choke, sv, loss, and var values.
When sv dips, your CPU is probably pegged out. Choke is the server
holding back packets. Loss is obvious. Var is basically jitter.
Be sure that your client is configured like this, no matter what your
real network connection is (That is, set it to 10M/max). I've had lots
of users complain of lag and this fixed it for them;
http://whisper.ausgamers.com/wiki/index.php/Bad_choke_solution
You will see a lot of bad advice out there about compiling your kernel,
realtime, and other garbage. THere are a lot of very eager-to-please
noob kids who want to run servers, but they don't know squat about being
a sysadmin.
You are running a very modern kernel on amd64; that's good.
Could be some BIOS thing. Set it to defaults and don't fark with it
unless you know what you are doing.
Go back to the first thing I wrote on this email, and kick yourself for
wasting money AND getting slower hardware than you could have had.
Those Opterons are good for "wide" multi-threaded multi-user type
applications, but that isn't what srcds is.
Good luck
frog wrote:
We've got dedicated server, 6 x 2.3ghz (AMD Opteron 6276), 16GB RAM, 200GB HDD,
which struggles to run a full 24 slot TF2 server smoothly.
--
# Jesse Molina
# Mail = [email protected]
# Page = [email protected]
# Cell = 1.602.323.7608
# Web = http://www.opendreams.net/jesse/
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
