History log of /external/skia/tools/test_gpuveto.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
12c2198535759ee9aae91ec385e8e31e5dbc12d7 18-Jun-2014 egdaniel <egdaniel@google.com> Remove dashing from gpu veto

With new veto our new veto test results look like the following:
TP: true positive (picked to use gpu and gpu was faster)
I: inderminate, the raster time is withing 5% of gpu time

TP FP TN FN I

old 21 9 15 12 3
new 29 12 11 6 3

There are three skps that tend to move from TN -> FP, however
the absolute difference in their run times are not huge between
them. The largest being desk_booking which is about 7.1 raster
and 8.8 gpu. The other two skps are desk_yahooanswers and
desk_linkedin

BUG=skia:
R=bsalomon@google.com, robertphillips@google.com

Author: egdaniel@google.com

Review URL: https://codereview.chromium.org/334053005
/external/skia/tools/test_gpuveto.py
bde3cd8f1d0c57fc2831f1ada4c55fca60233a88 28-Apr-2014 commit-bot@chromium.org <commit-bot@chromium.org@2bbb7eff-a529-9590-31e7-b0007b416f81> First version of gpuveto testing script

This CL just sketches out the structure of the gpuveto testing process. Two big areas for improvement are:
render the picture in tiles and label as unsuitable if any gpu tile is slower than raster
decide on whether tilegrid is used or not

As expected the current gpuveto heuristic isn't so good:

predicted suitable unsuitable
-------------------------------------------
actual suitable 10 17
actual unsuitable 15 27

R=rmistry@google.com, bsalomon@google.com

Author: robertphillips@google.com

Review URL: https://codereview.chromium.org/257723003

git-svn-id: http://skia.googlecode.com/svn/trunk@14416 2bbb7eff-a529-9590-31e7-b0007b416f81
/external/skia/tools/test_gpuveto.py