Timings Viewer

PocketMine-MP Version 5.21.1
Sample time 3.08 h (Ticks: 195652)
Main thread CPU time spent 2.11 h
Average Entities 181.95
Average Players 180.06
Average TPS 17.65
Main Thread Load 68.57%
Submitted 2024-11-28 20:30:56 +00:00
View raw

Notice: Your AVG TPS is less than 19 but server load is less than 95.
This means that something (not the server's main thread) is hogging the CPU. This might be because of overloaded AsyncWorkers (plugins scheduling too many AsyncTasks or AsyncTasks running for too long), too much activity on the network, or something else might be running on the machine and hogging the CPU. You should check the machine's overall CPU usage to see if anything else might be using a lot of CPU.
Minecraft (Tree View) Total: 2.111 h Pct: 68.57%
Event % Total Time ÷ Count Violations Peak Count ÷ Ticks Count
Full Server Tick[?]		 68.57% 10.43 ms 55.4k 2.78 s 3.7 729.0k
Server Tick Update Cycle		 47.62% 26.98 ms 45.4k 787.34 ms 1.0 195.7k
Worlds - World Tick		 44.91% 25.44 ms 38.6k 201.43 ms 1.0 195.7k
Connection Handler[?]		 2.49% 1.41 ms 214 746.31 ms 1.0 195.7k
[self][?]		 0.07% 37.14 μs 6.6k N/A 1.0 195.7k
Scheduler[?]		 0.06% 31.96 μs 0 2.95 ms 1.0 195.7k
Server Command		 0.02% 13.42 μs 4 239.48 ms 1.0 195.7k
Scheduler - Async Tasks		 0.02% 12.31 μs 0 2.54 ms 1.0 195.7k
Player Data Save		 0.02% 376.04 μs 29 3.23 ms 0.0 5.9k
Memory Manager		 0.01% 6.85 μs 19 280.09 ms 1.0 195.7k
Worlds - Data Save		 0.01% 28.80 ms 11 368.59 ms 0.0 32
Server Mid-Tick Processing		 20.96% 4.35 ms 4.7k 2.78 s 2.7 533.4k
Snooze Handler: closure@pmsrc/src/network/mcpe/raklib/RakLibInterface#L104		 20.69% 4.39 ms 4.4k 2.73 s 2.7 522.2k
[self][?]		 0.12% 24.36 μs 92 N/A 2.7 533.4k
Snooze Handler: closure@plugins/Middleware/src/SenseiTarzan/Middleware/libs/SenseiTarzan/Mongodm/MongodmManager#L50		 0.09% 27.26 ms 128 839.30 ms 0.0 373
Snooze Handler: closure@pmsrc/src/scheduler/AsyncPool#L126		 0.05% 574.39 μs 14 40.63 ms 0.1 10.0k
Snooze Handler: closure@/home/container/virions/libredis/src/SenseiTarzan/libredis/RedisManager#L66		 0.01% 309.07 μs 3 133.33 ms 0.0 2.5k
Minecraft Total: 2.111 h Pct: 68.57%
Event % Total Time ÷ Count Violations Peak Count ÷ Ticks Count
Full Server Tick[?] 68.57% 10.43 ms 55.4k 2.78 s 3.7 729.0k
Server Tick Update Cycle 47.62% 26.98 ms 45.4k 787.34 ms 1.0 195.7k
Worlds - World Tick 44.91% 25.44 ms 38.6k 201.43 ms 1.0 195.7k
world - World Tick 44.91% 25.44 ms 38.6k 201.43 ms 1.0 195.7k
Worlds - Entity Tick 43.31% 24.54 ms 35.0k 150.20 ms 1.0 195.7k
world - Entity Tick 43.31% 24.54 ms 35.0k 150.20 ms 1.0 195.7k
Entity Tick - Player 42.87% 134.88 μs 33.7k 14.31 ms 180.1 35.2M
checkNearEntities 37.83% 119.07 μs 13.9k 14.29 ms 180.0 35.2M
Connection Handler (25 combined)[?] 23.30% 1.84 ms 4.7k 2.73 s 7.2 1.4M
Server Mid-Tick Processing 20.96% 4.35 ms 4.7k 2.78 s 2.7 533.4k
Show 242 more rows
Events Total: 32.943 m Pct: 17.83%
Event % Total Time ÷ Count Violations Peak Count ÷ Ticks Count
PlayerChatEvent 17.57% 891.65 μs 3.6k 15.41 ms 11.2 2.2M
DataPacketReceiveEvent (20 combined) 0.20% 9.13 μs 5 12.01 ms 12.2 2.4M
DataPacketSendEvent (115 combined) 0.05% 3.97 μs 18 896.70 μs 7.5 1.5M
PlayerJoinEvent 0.01% 1.79 ms 3 98.97 ms 0.0 725
PlayerQuitEvent (2 combined) 0.00% 315.66 μs 2 10.10 ms 0.0 798
Show 41 more rows
Testlibredis v0.1 Total: 32.187 m Pct: 17.42%
Event % Total Time ÷ Count Violations Peak Count ÷ Ticks Count
SenseiTarzan\redistest\Main‑>onChat(PlayerChatEvent) 17.41% 883.63 μs 3.6k 15.40 ms 11.2 2.2M
SenseiTarzan\redistest\Main‑>onJoin(PlayerJoinEvent) 0.01% 1.79 ms 3 98.95 ms 0.0 725
SenseiTarzan\redistest\Main‑>onQuit(PlayerQuitEvent) (2 combined) 0.00% 303.91 μs 2 10.05 ms 0.0 798
Middleware v0.0.2 Total: 11.210 s Pct: 0.10%
Event % Total Time ÷ Count Violations Peak Count ÷ Ticks Count
SenseiTarzan\Middleware\Listener\PacketListener‑>onDataReceive(DataPacketReceiveEvent) (20 combined) 0.10% 4.70 μs 5 12.00 ms 12.2 2.4M
MultiEconomy v1.0.3 Total: 2.401 s Pct: 0.02%
Event % Total Time ÷ Count Violations Peak Count ÷ Ticks Count
closure@plugins/MultiEconomy_dev-26.phar/src/SenseiTarzan/MultiEconomy/libs/CortexPE/Commando/libs/muqsit/simplepackethandler/interceptor/PacketInterceptorListener#L72(DataPacketSendEvent) (115 combined) 0.01% 833.84 ns 0 595.74 μs 7.5 1.5M
SenseiTarzan\MultiEconomy\libs\SenseiTarzan\LanguageSystem\Listener\PacketListener‑>onSendPacket(DataPacketSendEvent) (116 combined) 0.01% 798.39 ns 0 768.99 μs 7.5 1.5M
Show 2 more rows
DEVirion v1.3.0 Total: 1.620 s Pct: 0.01%
Event % Total Time ÷ Count Violations Peak Count ÷ Ticks Count
Task: anonymous@plugins/DEVirion_dev-45.phar/src/poggit/virion/devirion/DEVirion#L101(interval:1) 0.01% 8.28 μs 0 2.80 ms 1.0 195.7k
© Aikar of Empire Minecraft 2017
© PMMP Team 2017-2023
[source]
Connection Handler (previously labeled Player Tick) includes a wide variety of other things, such as sending network packets, handling incoming network packets, packet compression, and packet encryption.

Since received packets can trigger a wide variety of other events (e.g. PlayerMoveEvent, PlayerInteractEvent, EntityDamageByEntityEvent, BlockPlaceEvent, BlockBreakEvent), a high value for this entry might indicate performance problems in plugins, or it may mean that your server simply can't handle the number of players online.

Look for plugin event timings to see if any of them might be causing performance problems.
Full Server Tick is the total of all other timers. If this hits 100%, your server will begin losing TPS.

Full Server Tick cannot be improved directly. Look at other timers to find out where time is being spent.
Scheduler is the total of all Task timings. This includes all time spent running plugin tasks. Look at "Task: " entries to find out which tasks are taking the most time.

Note: Async Tasks are not counted here, since they run in a separate thread.
Self Timings account for time when the parent timer was active, but none of its child timers were active. For example, Entity Movement might use specialized timers to cover certain parts of the movement code, leaving the remainder to self timings.
This timer accounts for the combined CPU time spent by all server Async Task worker threads. This is subdivided into timings for individual async tasks. High numbers here don't directly affect TPS and usually aren't a cause for concern. However, slow async tasks can cause other problems, such as delayed terrain loading.

You might see very large Pct Total numbers here. A value of 100% means that async tasks are maxing out 1 CPU core on average. It will be larger than 100% if multiple workers (and therefore multiple CPU cores) are being used. For example, if you have 4 async workers and they are all maxed out, you would see a value close to 400%.