1. 29 Sep, 2019 2 commits
  2. 28 Sep, 2019 1 commit
  3. 26 Sep, 2019 2 commits
  4. 24 Sep, 2019 1 commit
  5. 19 Sep, 2019 1 commit
  6. 17 Sep, 2019 1 commit
  7. 16 Sep, 2019 2 commits
  8. 29 Aug, 2019 2 commits
  9. 26 Aug, 2019 1 commit
  10. 20 Aug, 2019 1 commit
  11. 31 Jul, 2019 1 commit
  12. 26 Jul, 2019 3 commits
  13. 24 Jul, 2019 1 commit
  14. 23 Jul, 2019 2 commits
  15. 18 Jul, 2019 1 commit
  16. 17 Jul, 2019 2 commits
  17. 10 Jul, 2019 1 commit
  18. 09 Jul, 2019 1 commit
  19. 08 Jul, 2019 1 commit
  20. 03 Jul, 2019 1 commit
  21. 02 Jul, 2019 1 commit
  22. 28 Jun, 2019 2 commits
  23. 27 Jun, 2019 1 commit
  24. 25 Jun, 2019 1 commit
    • Jim Graham's avatar
      Add test case for Flutter Issue #27677 as a benchmark. (#34870) · f83fd9d4
      Jim Graham authored
      * Add test case for Flutter Issue #27677 as a benchmark.
      
      See https://github.com/flutter/flutter/issues/27677
      
      I got the following results running the test on a Moto E2 which
      will help us determine how much we can gain by analyzing the
      operations and eliminating unnecessary repaints based on
      dirty rectangles/regions.
      
      no blurs       - avg 216.0 fps over 3 samples
      blur the group - avg  22.9 fps over 3 samples
      blur each txt  - avg   3.4 fps over 3 samples
      
      * Added the new benchmark to be tracked on the dashboard.
      f83fd9d4
  25. 24 Jun, 2019 1 commit
  26. 12 Jun, 2019 1 commit
  27. 10 Jun, 2019 1 commit
  28. 07 Jun, 2019 2 commits
  29. 05 Jun, 2019 1 commit
  30. 04 Jun, 2019 1 commit