You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's a file where I write mllisecond timings to a file. Yes. the json is supposed to be in microseconds. But Perfetto has the "raw" timestamp format which should show 52.497, but instead shows and adjusts the timeline to scale 52497. This ignores the decimal point. The graph then isn't marked to the correct millisecond timings.
So these are being converted to nanos and displayed as such, but that wasn't the goal of the original output. So raw really mean nanos, not the raw values in microseconds. But then there isn't a microsecond scale which would also fix this.
Trying to use the seconds formatter, these display as [0.0052497 s] if I write them as the expected microsecond integers. Which also isn't a great scale either.
I've brought this up in past issues, that the time formatting is missing a milliseconds (and microseconds but I never work in those) format which is how I time most rendering. We deal with 30Hz to 240Hz displays.
Just make sure the hover tip reflects the correct unit if you didn't do so already. That's a critical utility for me, and I'm really pleased that was added.
This CL changes the "raw" and "rawlocale" timestamps to instead
reference "trace nanoseconds" instead. This makes it much clearer to
users who might be generating JSON traces where the "raw" timestamps in
the trace might be in millis or micros.
Bug: #879
Change-Id: Ib904d1fa95d87eb6f747bb8badbc9947daf88d10
Here's a file where I write mllisecond timings to a file. Yes. the json is supposed to be in microseconds. But Perfetto has the "raw" timestamp format which should show 52.497, but instead shows and adjusts the timeline to scale 52497. This ignores the decimal point. The graph then isn't marked to the correct millisecond timings.
So these are being converted to nanos and displayed as such, but that wasn't the goal of the original output. So raw really mean nanos, not the raw values in microseconds. But then there isn't a microsecond scale which would also fix this.
Trying to use the seconds formatter, these display as [0.0052497 s] if I write them as the expected microsecond integers. Which also isn't a great scale either.
I've brought this up in past issues, that the time formatting is missing a milliseconds (and microseconds but I never work in those) format which is how I time most rendering. We deal with 30Hz to 240Hz displays.
The text was updated successfully, but these errors were encountered: