Need server expert: CPU time usage.
- Thread starter Shevron
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
Oh wow I though tps was 20 tps or less not measured in ms since that usually referred as bandwidth. However I think Lambhost want FragNet out of the water
07.02 22:47:59 [Server] INFO Overall : Mean tick time: 7.746 ms. Mean TPS: 20.000
07.02 22:47:59 [Server] INFO Dim 0 : Mean tick time: 7.325 ms. Mean TPS: 20.000
07.02 22:47:59 [Server] INFO Dim 1 : Mean tick time: 0.132 ms. Mean TPS: 20.000
07.02 22:47:59 [Server] INFO Dim -1 : Mean tick time: 0.236 ms. Mean TPS: 20.000
Thanks for the command.
07.02 22:47:59 [Server] INFO Overall : Mean tick time: 7.746 ms. Mean TPS: 20.000
07.02 22:47:59 [Server] INFO Dim 0 : Mean tick time: 7.325 ms. Mean TPS: 20.000
07.02 22:47:59 [Server] INFO Dim 1 : Mean tick time: 0.132 ms. Mean TPS: 20.000
07.02 22:47:59 [Server] INFO Dim -1 : Mean tick time: 0.236 ms. Mean TPS: 20.000
Thanks for the command.
1 second divided by 20 is 0.050s, which is 50ms.
"07.02 22:47:59 [Server] INFO Dim 0 : Mean tick time: 7.325 ms. Mean TPS: 20.00" means that the server is managing to compute a tick in 7.325ms, which is great.
When that time goes above 50ms, your tps rate starts to drop, because it's can't keep the minimum optimal rate of 20 ticks a second. With the previous host, just me on the map, I was seeing 46ms. On this one, 8ms with 3 players online with all their machines whirring around, I say it's a huge improvement
"07.02 22:47:59 [Server] INFO Dim 0 : Mean tick time: 7.325 ms. Mean TPS: 20.00" means that the server is managing to compute a tick in 7.325ms, which is great.
When that time goes above 50ms, your tps rate starts to drop, because it's can't keep the minimum optimal rate of 20 ticks a second. With the previous host, just me on the map, I was seeing 46ms. On this one, 8ms with 3 players online with all their machines whirring around, I say it's a huge improvement
1 second divided by 20 is 0.050s, which is 50ms.
"07.02 22:47:59 [Server] INFO Dim 0 : Mean tick time: 7.325 ms. Mean TPS: 20.00" means that the server is managing to compute a tick in 7.325ms, which is great.
When that time goes above 50ms, your tps rate starts to drop, because it's can't keep the minimum optimal rate of 20 ticks a second. With the previous host, just me on the map, I was seeing 46ms. On this one, 8ms with 3 players online with all their machines whirring around, I say it's a huge improvement
Wow thanks for the explanation! But both forge tps and gc are saying difference things so is forge tps is the better way to go with checking the rate the server is running at?
I always used forge tps to know what happening, and always proved right so far.
As long as all dimensions are under 50ms, your tps rate will stay at 20, which is the clock by which everything happens. Why 50ms? Mob movement, machines cycles, furnaces .. everything runs against the 20 tps clock. When the server resources get overloaded and goes to, let's say 60ms, 60 x 20 = 1.2 seconds, so now the server is taking 1.2 seconds to perform what was supposed to get done in 1 second. Chests take long to open, pressure plates delay and you start getting stuck in doors and mobs start teleporting around.
So the lower that number in ms is, the better your server is coping. 7ms is an exceedingly good time!
So yeah, since forge tps gives you your tps count of that instant, I say it's a fairly good and accurate tool
Look into Opis if you want to explore more what's going on with the timings of your server. I found it a fun learning tool of what does what, even when my server was running smoothly.
As long as all dimensions are under 50ms, your tps rate will stay at 20, which is the clock by which everything happens. Why 50ms? Mob movement, machines cycles, furnaces .. everything runs against the 20 tps clock. When the server resources get overloaded and goes to, let's say 60ms, 60 x 20 = 1.2 seconds, so now the server is taking 1.2 seconds to perform what was supposed to get done in 1 second. Chests take long to open, pressure plates delay and you start getting stuck in doors and mobs start teleporting around.
So the lower that number in ms is, the better your server is coping. 7ms is an exceedingly good time!
So yeah, since forge tps gives you your tps count of that instant, I say it's a fairly good and accurate tool
Look into Opis if you want to explore more what's going on with the timings of your server. I found it a fun learning tool of what does what, even when my server was running smoothly.