| commit | 9beafc41afa3c78ffa12649dcde73628c277da9c | [log] [tgz] |
|---|---|---|
| author | Mike Klein <mtklein@chromium.org> | Mon Jun 05 06:32:21 2017 -0400 |
| committer | Skia Commit-Bot <skia-commit-bot@chromium.org> | Mon Jun 05 13:46:40 2017 +0000 |
| tree | f55d4428c25e412f78d8bfee3d321809f7826702 | |
| parent | 34d10d734c883758576f3473c5ac38be20c1e99f [diff] |
have start_pipeline() return limit again
This is spooky.
I don't quite yet understand why, but this makes things much faster.
Performance regressed across the board when we no longer needed the
value and changed it to return void:
https://perf.skia.org/e/?begin=1496176469&keys=6994&xbaroffset=28513
You can see similar regressions following this Chromium bug link.
BUG=chromium:729237
Change-Id: I68371b0456014f909acf819aca52aa4f4f187460
Reviewed-on: https://skia-review.googlesource.com/18580
Reviewed-by: Herb Derby <herb@google.com>
Reviewed-by: Mike Reed <reed@google.com>
Commit-Queue: Mike Klein <mtklein@chromium.org>