Open ljacqu opened 7 years ago
https://timings.spigotmc.org/?url=jeracesopa We are still having performance issues... (timings by @hsombini)
That was ASYNC
This is SYNC in a similar condition: https://timings.spigotmc.org/?url=ponopubufu
Log times to an additional file. Perhaps with https://www.infoq.com/articles/perf4j?
Perf4J looks very outdated, what about that? http://metrics.dropwizard.io/3.2.0/index.html
@sgdc3 Looks nice! I'm all for it.
It looks normal to me, isAuthAvailable is called when players join. we already cache the value to save performance
People are refusing to update from 3.4 to 5.2 due to performance issues, we can't ignore the problem.
I'm now personally using 5.4 on my network, never experienced lag issues caused by authme, my timings looks fine. I'll move this to 5.5
from @sgdc3
This issue is for finding problems (improvements) regarding our performance. Once we have some figures we can create follow-up stories with concrete improvements.
1. Are we creating too many async tasks?
2. Where do we lose the most time?
3. Check database interactions