[cod] Disapointed
Luke
luke at techfreak.org
Tue Nov 25 17:16:25 EST 2003
Yup. Doesnt appear to be a resource issue, then. Must be
your network connection? any chance that might be the
bottleneck?
Luke
MayDay said:
> As you can see it's using 21% when theres 0 users on and 0
> CPU, theres 350MB
> free ram in that TOP.
>
> This is now with 8 users on:
>
> top - 22:12:07 up 13:29, 1 user, load average: 0.32,
> 0.21, 0.22
> Tasks: 58 total, 2 running, 56 sleeping, 0 stopped,
> 0 zombie
> Cpu(s): 8.3% us, 0.7% sy, 0.0% ni, 89.1% id, 0.0% wa,
> 1.0% hi, 1.0% si
> Mem: 516664k total, 219112k used, 297552k free,
> 2256k buffers
> Swap: 358840k total, 0k used, 358840k free,
> 78620k cached
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM
> TIME+ COMMAND
> 1152 clan 15 0 214m 115m 3084 S 8.3 22.8
> 6:03.71 cod_lnxded
>
> 23% Mem and 5-15% CPU
>
> I don't intend to run more than it's running now so why
> should i increase
> the swap if it will never use it ?
>
> //MD
>
> ----- Original Message -----
> From: "Joe Brown" <joe at overdrivepc.com>
> To: <cod at icculus.org>
> Sent: Tuesday, November 25, 2003 9:19 PM
> Subject: Re: [cod] Disapointed
>
>
>> MayDay wrote:
>>
>> >TOP: Sorted after Memory.
>> >
>> >All the extra services i started like udpb, codbot,
>> uglygs, apache i
> tried
>> >to shut down aswell as server logging, still lags.
>> >
>> >
>> >top - 20:09:48 up 11:26, 1 user, load average: 0.04,
>> 0.01, 0.00
>> >Tasks: 58 total, 2 running, 56 sleeping, 0
>> stopped, 0 zombie
>> >Cpu(s): 1.1% us, 0.5% sy, 0.0% ni, 97.3% id, 0.0%
>> wa, 0.5% hi, 0.5%
> si
>> >Mem: 516664k total, 196200k used, 320464k free,
>> 2220k buffers
>> >Swap: 358840k total, 0k used, 358840k free,
>> 62012k cached
>> >
>> > PID USER PR NI VIRT RES SHR S %CPU %MEM
>> TIME+ COMMAND
>> > 857 clan 15 0 214m 109m 3084 S 0.0 21.7
>> 2:43.96 cod_lnxded
>> > 346 www-data 16 0 72060 3404 69m S 0.0 0.7
>> 0:00.00 apache
>> > 694 www-data 15 0 72068 3404 69m S 0.0 0.7
>> 0:00.00 apache
>> > 864 clan 15 0 5216 3380 3896 S 0.0 0.7
>> 0:00.14 python
>> >
>> >
>> You're sure you weren't using the leaked version of
>> cod_lnxded?
>>
>> Sounds like a memory issue to me. Tiny swapspace
>> probably not helping
>> the issue, but it sounds like your dealing with a memory
>> contention of
>> some sort.
>> 62mb cached -- that's not much file caching, Linux uses
>> practically all
>> free memory for file caching. Based on this snapshot,
>> almost all memory
>> is in use.
>>
>> When disk swapping is taking place, cpu resources will
>> likely be
>> minimal, because the cpu can't much of anything with
>> swapped out memory..
>>
>> ---
>> Here's top from the server I manage, running 3 cod linux
>> servers on a p4
>> 2.4ghz box (note these are all the processes currently
>> running on this
> box)
>> Red Hat Linux release 7.3 (Valhalla)
>> 69.57.130.53:28960 (tdm), 29862 (sd), 29864 (re) if your
>> interested in
>> experimenting w/them to compare lag. Each server
>> remains packed w/20
>> ppl pretty much all day, since the linux release became
>> available. This
>> server is kinda maxed (could use more memory, cod is a
>> memory monger
>> compared to q3), but runs pretty good, as best I can
>> tell....
>>
>> 3:05pm up 4 days, 22:36, 1 user, load average: 0.65,
>> 0.47, 0.55
>> 36 processes: 33 sleeping, 3 running, 0 zombie, 0
>> stopped
>> CPU states: 38.7% user, 1.8% system, 0.0% nice, 59.4%
>> idle
>> Mem: 506048K av, 496928K used, 9120K free,
>> 0K shrd, 17120K
>> buff
>> Swap: 1020116K av, 175224K used, 844892K free
>> 89552K
>> cached
>>
>> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM
>> TIME COMMAND
>> 9214 cod1 20 -5 131M 127M 1464 R < 40.0 25.7
>> 130:04 cod_lnxded
>> 9234 cod2 7 -5 129M 103M 1464 S < 0.0 20.9
>> 19:24 cod_lnxded
>> 9248 cod3 7 -5 131M 101M 1464 S < 0.0 20.4
>> 15:08 cod_lnxded
>> 10851 root 9 0 1676 1624 1288 R 0.0 0.3
>> 0:00 sshd
>> 2551 nobody 9 0 2248 1524 1252 S 0.0 0.3
>> 0:02 httpd
>> 2550 nobody 9 0 2244 1520 1248 S 0.0 0.3
>> 0:02 httpd
>> 10852 root 9 0 1328 1328 1000 S 0.0 0.2
>> 0:00 bash
>> 18488 cod1 9 0 1852 1156 840 S 0.0 0.2
>> 0:07 python2
>> 10885 root 9 0 1056 1056 868 R 0.0 0.2
>> 0:00 top
>> 1024 cod1 7 -5 1232 924 820 S < 0.0 0.1
>> 0:00 screen
>> 839 cod3 7 -5 1048 880 876 S < 0.0 0.1
>> 0:00 bash
>> 915 cod2 7 -5 1048 880 876 S < 0.0 0.1
>> 0:00 bash
>> 1026 cod1 7 -5 1044 880 876 S < 0.0 0.1
>> 0:00 bash
>> 837 cod3 7 -5 1116 876 780 S < 0.0 0.1
>> 0:00 screen
>> 914 cod2 7 -5 1116 876 780 S < 0.0 0.1
>> 0:00 screen
>> 2664 root 9 0 696 560 484 S 0.0 0.1
>> 0:01 sshd
>> 2544 root 9 0 1396 532 516 S 0.0 0.1
>> 0:01 httpd
>> 999 root 8 0 552 512 464 S 0.0 0.1
>> 0:00 crond
>> 931 root 9 0 616 448 444 S 0.0 0.0
>> 0:00 xinetd
>> 699 root 9 0 492 444 408 S 0.0 0.0
>> 0:00 syslogd
>> 1 root 9 0 420 376 356 S 0.0 0.0
>> 0:06 init
>> 704 root 9 0 416 360 356 S 0.0 0.0
>> 0:00 klogd
>> 1261 root 9 0 384 324 320 S 0.0 0.0
>> 0:00 agetty
>> 1260 root 9 0 332 280 276 S 0.0 0.0
>> 0:00 mingetty
>> 2 root 9 0 0 0 0 SW 0.0 0.0
>> 0:00 keventd
>> 3 root 9 0 0 0 0 SW 0.0 0.0
>> 0:01 kapmd
>> 4 root 19 19 0 0 0 SWN 0.0 0.0
>> 0:00
> ksoftirqd_CPU0
>> 5 root 9 0 0 0 0 SW 0.0 0.0
>> 0:13 kswapd
>> 6 root 9 0 0 0 0 SW 0.0 0.0
>> 1:28 kscand
>> 7 root 9 0 0 0 0 SW 0.0 0.0
>> 0:00 bdflush
>> 8 root 9 0 0 0 0 SW 0.0 0.0
>> 0:00 kupdated
>> 9 root -1 -20 0 0 0 SW< 0.0 0.0
>> 0:00 mdrecoveryd
>> 13 root 9 0 0 0 0 SW 0.0 0.0
>> 0:05 kjournald
>> 92 root 9 0 0 0 0 SW 0.0 0.0
>> 0:00 khubd
>> 287 root 9 0 0 0 0 SW 0.0 0.0
>> 0:00 kjournald
>> 601 root 9 0 0 0 0 SW 0.0 0.0
>> 0:00 eth0
>>
>>
>>
>>
>
More information about the Cod
mailing list