aboutsummaryrefslogtreecommitdiffhomepage
path: root/bench
diff options
context:
space:
mode:
authorGravatar commit-bot@chromium.org <commit-bot@chromium.org@2bbb7eff-a529-9590-31e7-b0007b416f81>2014-03-06 17:16:37 +0000
committerGravatar commit-bot@chromium.org <commit-bot@chromium.org@2bbb7eff-a529-9590-31e7-b0007b416f81>2014-03-06 17:16:37 +0000
commit1b28f6f1ce3de9bc5ef1182e94df11f9f5610913 (patch)
treee325637189a5ac803c4b6be537f8fb4be2add5cf /bench
parent490fb6b4713463954cc0283a9c30e754c45c6004 (diff)
Adding this call simulates seeing a *different* bitmap every time we scale, which changes the code path (places much heavier load on constructing a new filter). This better emulates the kind of environment most embedders see us in, where they try to cache a scaled bitmap rather than frequently rescaling it.
This change will cause significant regressions in microbenchmark scores. BUG=skia:2236 R=humper@google.com, reed@google.com, scroggo@google.com, tomhudson@google.com Author: tomhudson@chromium.org Review URL: https://codereview.chromium.org/183763047 git-svn-id: http://skia.googlecode.com/svn/trunk@13685 2bbb7eff-a529-9590-31e7-b0007b416f81
Diffstat (limited to 'bench')
-rw-r--r--bench/BitmapScaleBench.cpp1
1 files changed, 1 insertions, 0 deletions
diff --git a/bench/BitmapScaleBench.cpp b/bench/BitmapScaleBench.cpp
index 926111d12d..f6c2da17a9 100644
--- a/bench/BitmapScaleBench.cpp
+++ b/bench/BitmapScaleBench.cpp
@@ -97,6 +97,7 @@ protected:
SkPaint paint;
paint.setFilterLevel(SkPaint::kHigh_FilterLevel);
+ fInputBitmap.notifyPixelsChanged();
canvas.drawBitmapMatrix( fInputBitmap, fMatrix, &paint );
}
private: