Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stress testing and profiling #107

Open
lare96 opened this issue Nov 10, 2018 · 2 comments
Open

Stress testing and profiling #107

lare96 opened this issue Nov 10, 2018 · 2 comments
Labels
hard An issue that is hard to resolve. high priority An issue that should be resolved right away.
Milestone

Comments

@lare96
Copy link
Member

lare96 commented Nov 10, 2018

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.

@lare96 lare96 added high priority An issue that should be resolved right away. blocked An issue that cannot be resolved yet, usually because of another issue. hard An issue that is hard to resolve. labels Nov 10, 2018
@lare96 lare96 added this to the v1.0 milestone Nov 10, 2018
@lare96
Copy link
Member Author

lare96 commented Dec 13, 2018

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.

@lare96 lare96 modified the milestones: v1.0, v0.5 Dec 13, 2018
@lare96 lare96 removed the blocked An issue that cannot be resolved yet, usually because of another issue. label Dec 13, 2018
@lare96 lare96 pinned this issue Mar 29, 2019
@notjuanortiz
Copy link
Contributor

notjuanortiz commented Nov 6, 2019

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hard An issue that is hard to resolve. high priority An issue that should be resolved right away.
Projects
None yet
Development

No branches or pull requests

2 participants