On 2012/07/13 07:18:44, nduca wrote: > How do we validate the record times coming out ...
12 years, 4 months ago
(2012-07-13 07:19:52 UTC)
#3
On 2012/07/13 07:18:44, nduca wrote:
> How do we validate the record times coming out of this are comparable to the
> record times coming from a real C++ source?
Is this a matter of
bench_pictures.recordTime - replayer.drawPictureToNullCanvas()?
On 2012/07/13 07:19:52, nduca wrote: > On 2012/07/13 07:18:44, nduca wrote: > > How do ...
12 years, 4 months ago
(2012-07-13 17:13:31 UTC)
#4
On 2012/07/13 07:19:52, nduca wrote:
> On 2012/07/13 07:18:44, nduca wrote:
> > How do we validate the record times coming out of this are comparable to the
> > record times coming from a real C++ source?
>
> Is this a matter of
>
> bench_pictures.recordTime - replayer.drawPictureToNullCanvas()?
So, I don't quite understand the issue. Are we worried that a program with calls
like
SkPicture recorder;
recordingCanvas* = recorder.beginRecording();
recordingCanvas->command();
recordingCanvas->command();
would have different timings from
SkPicture recorder;
recordingCanvas* = recorder.beginRecording();
recordingCanvas->drawPicture(somePicture);
where somePicture is the equivalent of the two recordingCanvas->commands() from
above?
On 2012/07/13 20:03:36, nduca wrote: > Yep. Presumably there's some playback overhead in there that ...
12 years, 4 months ago
(2012-07-13 21:23:31 UTC)
#6
On 2012/07/13 20:03:36, nduca wrote:
> Yep. Presumably there's some playback overhead in there that the raw program
> won't have? How bad is it?
The playback overhead is very lightweight. All objects required for playback
are pre-unflattened. So all playback does is execute bytecode. See
SkPicturePlayback::draw
Issue 6350102: bench_pictures now has an option for benchmarking record time.
(Closed)
Created 12 years, 4 months ago by keyar
Modified 12 years, 4 months ago
Reviewers: nduca, junov1
Base URL: https://skia.googlecode.com/svn/trunk
Comments: 0