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

Need guide on how to identify bottlenecks #182

Open
Laremere opened this issue Jun 30, 2020 · 0 comments
Open

Need guide on how to identify bottlenecks #182

Laremere opened this issue Jun 30, 2020 · 0 comments

Comments

@Laremere
Copy link
Contributor

From several discussions in slack, identifying the source of a bottleneck when running Open Match is not trivial. We should write a guide on finding and resolving bottlenecks within the system, including any of the services not receiving enough resources:

  • Frontend
  • Backend
  • Synchronizer
  • Redis
  • Evaluator
  • MMF

Additionally, the guide should go into how to use tracing to see how long various operation are taking.

I think it may be worth building a tool which can download all of the currently searching tickets via query API, and then re-create them in another system. This would allow for testing various configurations without having to using a live production service. It could also download the tickets over time, so you can generate an artificially large number of tickets based on real data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant