[PATCH] Retrace: Add per frame timing
jose.r.fonseca at gmail.com
Mon Oct 24 05:44:48 PDT 2011
On Sat, Oct 22, 2011 at 1:49 AM, Zack Rusin <zack at kde.org> wrote:
> On Friday, October 21, 2011 06:49:29 PM Anuj Phogat wrote:
>> Hi All,
>> Here is a simple patch to add per frame timing information while
>> retracing. Tested this patch with couple of simple applications. It seems
>> to work fine.
>> This will provide useful information to identify performance issues with a
>> specific frame. Currently, this patch creates a new file (frame.time) to
>> dump the per frame timings.
>> But the ideal way would be to integrate this information with apitrace UI.
>> I would try to understand the UI code and integrate this new feature.
> Yea, that would be a great feature to have. We've discussed it previously on
> this mailing list, you might want to go check out that discussion in the
> archives because there's quite a few things we'll need to do to get it right.
Yes. I was planning was to refactor the last patch that Yuanhan Liu
posted to this list such that the recording was done in glretrace
instead of apitrace, but been busy with other stuff.
My idea was to have glretrace output the timings to stdout in a TSV format like:
# call no function name cpu start cpu stop gpu start gpu stop
50 glDrawArrays 1.4 1.5 2.4 2.5
The GUI could then use this to produce a joint visualization of both
cpu and gpu timelines.
More information about the apitrace