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.

Sign up for GitHub

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

Jump to bottom

use more accurate measure of average for frametime #154

Open

tybug opened this issue Jun 27, 2020 · 0 comments

Contributor

tybug commented Jun 27, 2020

we use the median frametime currently, which can be misleading, for instance on a replay like this -

median could end up being right on the edge of one of the spikes and that information does not carry over into the value.

A better approach would be to split the (sorted) frametimes into 4 blocks, take the median of each, and then take the mean of the four medians.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment