1. 04 Oct, 2019 1 commit
  2. 15 Aug, 2019 1 commit
  3. 26 Jul, 2019 1 commit
  4. 29 Apr, 2019 1 commit
  5. 11 Apr, 2019 1 commit
  6. 12 Mar, 2019 1 commit
  7. 07 Mar, 2019 1 commit
  8. 01 Mar, 2019 3 commits
  9. 28 Feb, 2019 1 commit
    • liyuqian's avatar
      Add convex path and non-AA paint to shader warm-up (#28614) · f776cc19
      liyuqian authored
      One of our important client's SKP shows that this could improve one of
      their janky frame by 20ms. This also improves our
      flutter_gallery__transition_perf's worst frame time by ~20ms.
      
      On the other hand, 15ms has been added to the start-up latency. I guess
      it's a little faster to compile the shader on the start-up because we're
      compiling a lot of shaders there and the CPU cache must be hot.
      
      ## Related Issues
      
      https://github.com/flutter/flutter/issues/813
      f776cc19
  10. 27 Feb, 2019 1 commit
  11. 23 Feb, 2019 1 commit
  12. 22 Feb, 2019 1 commit
    • liyuqian's avatar
      Shader warm up (#27660) · a44f174e
      liyuqian authored
      This patch adds a default shader warm up process which moves shader compilation from the animation time to the startup time. This also provides an extension for `runApp` so developers can customize the warm up process.
      
      This should reduce our worst_frame_rasterizer_time_millis from ~100ms to ~20-30ms for both flutter_gallery and complex_layout benchmarks. Besides, this should also have a significant improvement on 90th and 99th percentile time (50%-100% speedup in some cases, but I haven't tested them thoroughly; I'll let our device lab collect the data afterwards).
      
      The tradeoff the is the startup time (time to first frame). Our `flutter run --profile --trace-startup` seems to be a little noisy and I see about 100ms-200ms increase in that measurement for complex_layout and flutter_gallery. Note that this only happens on the first run after install or data wipe. Later the Skia persistent cache will remove the overhead.
      
      This also adds a cubic_bezier benchmark to test the custom shader warm up process.
      
      This should fix https://github.com/flutter/flutter/issues/813 (either by `defaultShaderWarmUp`, or a `customShaderWarmUp`).
      a44f174e