Server Performance: Difference between revisions

Content added Content deleted
(justify text)
(rephrase networking part of xu_tps command)
Line 7: Line 7:
== Lag ==
== Lag ==
<div align="justify">
<div align="justify">
You can use <code>/xu_tps</code> on the client (type it in chat) to see if the server is experiencing ''tick lag'' – if the numbers are consistently red you have an issue. If they're continually white, but you're getting [[lag]], you may have FPS lag see [[Low End PCs]] for client performance tips. Keep in mind that <code>/xu_tps</code> is based on the connection between client and server, so the numbers could be impacted if you have high latency to the server. The 3 pairs of numbers are respectively the instantaneous ticktime, the rolling average ticktime over the last 100 game ticks, and the worst tick time over the last 100 ticks. Numbers in parentheses correspond to the equivalent in TPS. The example below shows a 30.30ms tick, and a drop to 7.84 TPS at some point in the last 100 ticks (roughly 5 seconds).
You can use <code>/xu_tps</code> on the client (type it in chat) to see if the server is experiencing ''tick lag'' – if the numbers are consistently red you have an issue. '''It should be noted that /xu_tps is basing its measures on time used by the server to respond to the client, which can be impacted with [[lag]].''' If they're continously white, but you're experiencing framerate issues, see [[Low End PCs]] for client performance tips. The 3 pairs of numbers are respectively the instantaneous ticktime, the rolling average ticktime over the last 100 game ticks, and the worst tick time over the last 100 ticks. Numbers in parentheses correspond to the equivalent in TPS. The example below shows a 30.30ms tick, and a drop to 7.84 TPS at some point in the last 100 ticks (roughly 5 seconds).
</div>
</div>