luna
luna copied to clipboard
Stress testing and profiling
Lastly, a stress test needs to be done in order to see if there are any bottlenecks that can be fixed. Will make another comment about the specifics closer to the v1.0 milestone completing.
I think I'll create a 0.5 release for when everything is done except cache stuff and combat, since this could be done before that as well.
If you're looking to benchmark a specific method's performance I would look into JMH. What exactly to benchmark, is up to you.
Stress testing would require us to create a stand-alone application that will simulate thousands of users and perform specific actions. This would be easy with a less-obfuscated client, but is still doable. Once we're able to simulate users and actions, we can profile the server application locally, using Java Mission Control or Java Flight Recorder, and locate any anomalies (memory leaks, bottlenecks, etc).