History

Make shader warm-up async so it can handle image (#28687 )

## Description

This moves another 15-20ms from the animation jank of one of our important client to the startup latency. Unfortunately, this is probably not captured in our current benchmarks (presumably some other bottlenecks overshadow this shader compilation in the worst_frame benchmark). Considering that drawing images is such a common operation, maybe we should add one in the future to benchmark this.

We need this PR to land soon for our client because this changes the API to return Future.

## Related Issues

https://github.com/flutter/flutter/issues/813

2019-02-28 20:07:55 -08:00

android

Revert "Upgrade the Gradle script to Android plugin version 3.3.0 (#26913 )" (#27045 )

2019-01-24 14:29:08 -08:00

ios

Roll engine to 05fee4eeee0ff6b219b1fcc394371e5f6963cc46 (#26713 )

2019-01-21 21:23:04 -08:00

lib

Reland "Shader warm up (#27660 )" (#28537 )

2019-02-27 09:33:08 -08:00

test_driver

Make shader warm-up async so it can handle image (#28687 )

2019-02-28 20:07:55 -08:00

pubspec.yaml

Add capability to run build_runner tests for engine (#28684 )

2019-02-28 20:06:14 -08:00

README.md

Add cull opacity perf test to device lab (#25381 )

2018-12-17 22:01:07 -08:00

README.md

Macrobenchmarks

Performance benchmarks using flutter drive.

Cull opacity benchmark

To run the cull opacity benchmark on a device:

flutter drive --profile test_driver/cull_opacity_perf.dart

Results should be in the file build/cull_opacity_perf.timeline_summary.json.

More detailed logs should be in build/cull_opacity_perf.timeline.json.