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
Performance measurements adjustments. #2494
Conversation
cramforce
commented
Mar 8, 2016
- Flush more often to make sure we don't miss important measurements.
- Shift framerate values, so that smaller values are better, because our reporting tool thinks these are ms.
@@ -127,9 +127,12 @@ export class Framerate { | |||
const duration = now - this.collectStartTime_; | |||
const framerate = 1000 / (duration / this.frameCount_); | |||
const performance = performanceFor(this.win); | |||
performance.tickDelta('fps', framerate); | |||
// We want good values to be low and CSI hates negative values, so we | |||
// shift everything by 60 and then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shift everything by 60 and then
...?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
@cramforce LGTM |
- Flush more often to make sure we don't miss important measurements. - Shift framerate values, so that smaller values are better, because our reporting tool thinks these are ms.
Wouldn't it be better to convert these to ms then? What we have now will cap |
@jridgewell I've thought about it, but the real answer there is to probably rethink this entire metric. The current approach is measuring too much time where nothing happens to make the averages meaningful in any way. |
Performance measurements adjustments.