Bukkit

onTime 4.1.3 @ Spigot 1.8.8 5f38d38-efd6cb0

Just noticed that onTime spends quite some time for the PlayerQuitEvent.
http://www0.xup.in/exec/ximg.php?fid=20383345
Average Players: 26.38 - Average TPS: 19.84 - Server Load:   29.18%

That's actually not an issue, just wanted to mention that.

I can provide a link to the complete Timing sheet via private message if needed.

Hi If this is still an issue for you, and you would like me to investigate please let me know.

Also, please provide a link to a copy of your config.yml so that I can understand how you are using OnTime and what portions could then be contributing to the high processor impact.

BR, Edge

Hey there,

sorry for the late response, honestly I did not expect an answer. The newest timings sample I took is not that worst, PlayerQuit has a PctTick at 250% with avarage 44 player over a time of 5400 seconds.

Anyway here is my config file. The paste will expire in one month from now.

http://pastebin.com/cehkASLL

Thanks for further investigating.

Cheers Krauti

I see you have online tracking enabled. Are you using this feature to feed a web page or other output?

I'm thinking this feature may be the source of the lag. Would you be willing to temporarily disable this function and see if this helps improve the performance of the playerQuitEvent?

Please update your config as follows, then reload Ontime plugin, and later provide an updated performance data.

If disabling this does help things, I'll know that this is where I should focus my efforts to create a fix.

Thanks, Edge

###################
# Online Tracking #
###################
 
# Enable if Online player status should be tracked in MYSQL Table
onlineTrackingEnable: false
 

Hey there,

basically I use the ingame output only to check how long someone has played on the server and/or when he/she joined the first time. There were and still are plans to use the collected information further, has low priority though. So I just keep on tracking ;).

Sure I could disable the online tracking for a while, but will this have any impact further than a small gap between the already collected stuff?

@Krauti2: Go

Hi, Disabling that function will not change any of the data collected. The 'online tracking' just creates a separate, supplemental MYSQL table that hosts status of players currently on the server. Some admins use this table to populate their web pages, but it has no direct baring on any OnTime functions, as any data found in this table is also in the main OnTime table.

In short you and your players will see no difference based on how you describe your use of the plugin.

Ah great. So I do not need this feature as I use server query to put such information on the webpage.

I will disable this and take new timing samples tomorrow. Stay tuned.

Seems like this caused the issue. Took another sample over 6200 seconds. Average Players: 40.01 - Average TPS: 19.78 - Server Load: 48.11%

OnTimes PlayerQuitEvent is now less than 5% Pct Tick instead of more than 200% earlier and 0,01% Pct Total.

@Krauti2: Go

Thanks for confirming my suspicion. I now know where to focus my efforts to improve the performance, and the documentation to explain this function. You probably will want to leave it disabled even after I update the plugin unless you change your methods to feed your web page.

Thanks!

I have to thank YOU for taking the time to investigate this and not least for this great plugin.