Sniper's Paradise!
Advanced Server TNT
(Testing and Tweaking)
Testing 101:
Using the TimeDemo for FPS(Frames per second):
Start-up Unreal.
Before entering into a game choose Tools / TimeDemo Statistics, or while in a game press esc and and the Tools/TimeDemo Statistics and then enter the game:
You will get some text and numbers on the righthand side of your screen similar to this:
........Avg 34.56
Last Sec 31.24
to be cont'd
Using the "stat fps" command to test your FPS(Frames per second):
Start-up Unreal.
Enter the game as a client (player or spectator).
Hit the Tab key.
To start type... stat fps
To stop type... stat fps
You will get some text and numbers at the very bottom of your screen similar to this:
FRAME=031.5 MSEC RENDER=023.6 MSEC NODES=026 POLYS=016
to be cont'd
Using the "stat global" command to test various items:
Start-up Unreal.
Enter the game as a client (player or spectator).
Hit the Tab key.
To start type... stat global
To stop type... stat global
You will get some text and numbers at the top section of your screen similar to this:
GLOBAL:
FRAME=28.2: GAME=04.7 CLI=23.6 BLIT=00.3 PLAT=00.5
SCRIPT=003.4 ACTOR=02.1 PATH=00.0 SEE=00.0 SPAWN=00.0 AUDIO=00.1
UN=00.0 MOVE=00.5 (4) NET=00.1
RENDER=19.7 MESH=10.8 POLV=00.6 ILLUM=00.1 OCC=03.0 FILT=00.9 EX=00.0
DECAL=00.2 DECALCLIP=00.1
DECAL#=4
to be cont'd
Using the "stat net" command to test your packet loss:
Start-up Unreal.
Enter the game as a client (player or spectator).
Hit the Tab key.
To start type... stat net
To stop type... stat net
You will get some text and numbers at the top lefthand side of your screen similar to this:
NET (IN/OUT):
......105..................PING
......108..................CHANNELS
..........0 .......0.......UNORDERED/SEC
.......0%......0%.....PACKET LOSS
........18.......22.....PACKETS/SEC
........50.......22..... BUNCHES/SECOND
....1589...1407..... BYTES/SEC
..20000..20000....NETSPEED
to be
cont'd
Using the "inject userflag 1" command to test your net speed:
Start-up Unreal.
Enter the game as a client (player or spectator).
Hit the Tab key.
To start type... inject userflag 1
To stop type... inject userflag 0
You will get some text and numbers at the top of your screen
similar to this:
"i=20
cli=1 act=0.4 (608) net=1.3 pv/c=80 re p/c=0 rp c/c=0"
This is what the numbers mean:
i=20
Server frame rate is 20 fps (frames per second).
cli=1
Clients
(players and/or spectators) connected via the network
act=0.4
Ticking actors takes 0.4 ms (millisceconds) per frame. The actor tick time. Basically how long in milliseconds the server spends
doing most gameplay related stuff, doing collision and physics, etc. The number in parentheses is the number of actors in the
level.
(608)
There are 608 actors in the level
net=1.3
Server network processing overhead per frame in ms. This is the amount of time spent sending and receiving data to network clients. So if the number is 20 and you have 10 players, that's 2 milliseconds per player.
pv/c=80
Potentially visible actors per client (average).
Steve
Polge@Epic...The important numbers here are the actor and network time. These comprise most of the processing time for a dedicated server. If your server is running at 20 fps, then a total time of 50 msec would equal 100% server cpu utilization (50msec x 20 = 1 sec).
So to further clarify we would do the math. Example:...
(act=0.4ms) plus (net=1.3ms)=1.7ms
1.7msX20fps=34ms/fps divided by 1000=.034seconds=3.4%
cpu utilization.
with more players in the game we now see...act=6 plus net=12
(act=6ms) plus (net=12 ms) =18 ms
18msX20fps=360ms/fps divided by 1000= .36seconds = 36% cpu utilization :)
Jack Porter@Epic...The deal here is what the server has to do in each frame (50ms). It could spend 15ms doing gameplay and 20ms sending/receiving data to clients - so that's 35ms. There's probably another 10ms of miscellaneous junk going on which isn't being recorded in those stats, so that 45ms. With a 50ms frame rate, the server then tells Windows it's got nothing to do for 5ms. So your average Windows CPU utilization will probably be around 90%!
You can get a pretty good idea if it's bandwidth or CPU which makes netplay on a particular server crappy, by checking out that
stat. If it is CPU, you'll give your players much better netplay by reducing the number of players on the server.
By: MutantKiller
All logos and trademarks are properties of their respective owners.
Unreal™ is a registered trademark of Epic Games Inc.
Privacy Policy
Website by
Powered by RUSH