<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body>
Hey man, thanks for the wealth of info. I think we have this
resolved. They replaced on of the CPU's on the box and it now seems to
be happy. We'll put a few more servers on there and keep our fingers
crossed.<br>
<br>
Thanks all for you help on this!<br>
<br>
Maverick<br>
<br>
James Landi wrote:<br>
<blockquote type="cite"
cite="mid20040304212735.XWSJ10652.lakemtao04.cox.net@mainbox">
<pre wrap="">>From Activision's FAQ site
The game has a program loop that is constantly handling game "events". The
loop gets an event, handles that event, gets an event, handles that event,
etc. That loop has to execute at a fairly constant rate for the game play to
be smooth. However, since that loop can be interrupted by other programs
running on the computer, or can be delayed when the game does some
time-consuming operation (like loading levels or bots from disk), there's
code in that loop that adjusts for small amounts of time lost to those
interruptions (call the interruptions "hitches"). Longer hitches cause
glitches in game play (you've probably seen those where your connection to a
server goes bad and everything starts jumping around).
When the game is running as a dedicated server, it warns you (via the
console log) of hitches longer than 500 msec. You'll probably see hitch
warnings as the game loads levels, loads bots, or other time consuming
operations. The hitch warnings can be ignored as long as they are small
amounts of time. However, large hitches will be noticed by the clients (with
the extreme case being a temporary disconnection).
They then give you instructions to shut down background processes
<a class="moz-txt-link-freetext" href="https://activision.custhelp.com/cgi-bin/activision.cfg/php/enduser/atvi_guid">https://activision.custhelp.com/cgi-bin/activision.cfg/php/enduser/atvi_guid</a>
e_system.php#2
Original link here:
<a class="moz-txt-link-freetext" href="https://activision.custhelp.com/cgi-bin/activision.cfg/php/enduser/std_adp.p">https://activision.custhelp.com/cgi-bin/activision.cfg/php/enduser/std_adp.p</a>
hp?p_sid=6WEqvv5h&p_lva=&p_faqid=11830&p_created=1068148417&p_sp=cF9zcmNoPTE
mcF9ncmlkc29ydD0mcF9yb3dfY250PTImcF9zZWFyY2hfdGV4dD1oaXRjaCB3YXJuaW5nJnBfc2V
hcmNoX3R5cGU9MyZwX3Byb2RfbHZsMT0xJnBfcHJvZF9sdmwyPTM2MSZwX3NvcnRfYnk9ZGZsdCZ
wX3BhZ2U9MQ**&p_li=
-Jim Landi
Rudedog
CoDadmin.com
-----Original Message-----
From: Maverick [<a class="moz-txt-link-freetext" href="mailto:me83143@earthlink.net">mailto:me83143@earthlink.net</a>]
Sent: Thursday, March 04, 2004 1:56 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:cod@icculus.org">cod@icculus.org</a>
Subject: Re: [cod] New Server problem/hitch warnings
I believe it has a separate video card. The first box that works great
has the same value. As far as CPU overloading, this is a dual Xeon with
1 CoD server and that's it. Any other suggestions on what configuration
issues might cause this? We've been looking network, but based on what
you've said about hitch warnings, that may be incorrect. I've seen the
hitch warnings correspond to the lag we're getting, so I know they're
related. Any other suggestions you might have would be greatly
appreciated, and thanks again for your help so far!
Maverick
Christopher Kunz wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Maverick wrote:
</pre>
<blockquote type="cite">
<pre wrap="">reg00: base=0x00000000 ( 0MB), size=1024MB: write-back, count=1
</pre>
</blockquote>
<pre wrap="">
That's OK if you don't have on-board video.
</pre>
<blockquote type="cite">
<pre wrap="">I'm assuming that's correct since the box has 1 GB of memory. This
matches the previous box that works just fine. The frame stuff is
network, correct? Or is it video related? I'm venturing into new
areas here, but that's a good thing!
</pre>
</blockquote>
<pre wrap="">
Hitch warnings are CPU related. So if your CPU is overloaded, it will
produce hitches in the server, noticeable as jumpy movement (aka
"lag") for the clients.
--ck
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>