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

Ability to benchmark / track metrics #77

Open
JTimNolan opened this issue Apr 11, 2018 · 1 comment
Open

Ability to benchmark / track metrics #77

JTimNolan opened this issue Apr 11, 2018 · 1 comment

Comments

@JTimNolan
Copy link

Need to decide KPIs that will be used for core development (type 1), for lance-based game development (type 2), and for tracking production deployment stats (type 3). Probably want a unified API for tracking / reporting these stats. Personally I think it makes sense to start with a focus on lance core development as it will be immediately useful. Some metrics already suggested in slack:

Core KPI / Type 1:

  • Network usage
  • Server tick speed w/o extrapolation (we will probably need to have one/several standardized configurations for this to work for core dev benchmarking, but I think it's still useful. If not this, we'll need another way to benchmark the speed/efficiency of the lance core and any connectors we build)

Type 2 metrics:

  • FPS
  • Client tick speed
  • Server tick rate w/ extrapolation

Type 3 metrics:

  • latency

Please share other metrics that would be useful and implementation suggestions.

@namel
Copy link
Member

namel commented May 8, 2018

Would be great to have a pull request on this one, and in general any test suites that we can run.

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

2 participants