High timings on PlayerJoinListener
Farsinuce opened this issue ยท 7 comments
I got a high timings reading on Autorank v3.3-Dev-290 (556.70% Pct tick)
http://timings.aikar.co/?url=8627870
Is this normal or did I stumble upon a bug of sorts?
Running the lastest Spigot + Bungeecord of date.
I see no errors in the console.
Kind regards,
Sinuce
Could you try the latest dev version? I changed some things that were handled in the playerjoin listener, so it should run smoother.
Dev build link: http://62.131.38.74:8080/job/Autorank%20Beta/lastSuccessfulBuild/
I notice that after the above-mentioned upgrade, the player local playtime is reset, and the global playtime value seems off.
Do I need to recreate the database with this update?
Whoa, that's a lot of update activity :)
I'll upgrade to build #305, get some timings and report back here in approx. 24-48 hours.
Thank you.
It shouldn't have changed things around, but as it did, it is best to reset it completely.
The database has the exact same tables etc. with no difference from the previous version, so like you said, that part haven't changed things around.
However, going back to the former state with the previous database, the players' playtime has still been reset globally and decreased locally.
This is a different problem than this topic's original issue (#137).
Should I PM you onwards or should I open a New issue?
EDIT:
I haven't read any out-of-the-ordinary timings on Autorank since I updated to the Dev version you described. So I consider this (original) issue fixed. Thank you.