-
Notifications
You must be signed in to change notification settings - Fork 1
Dashboards
The index of Flutter dashboards is available at: https://flutter-dashboard.appspot.com/
There are two, one for benchmarks derived from running flutter/flutter tests, and one derived from flutter/engine tests.
Each data set (results from a benchmark value) consists of date/value pairs associated with a set of parameters. These parameters include things like the branch that was being tested, the benchmark test name ("test"), and the specific value ("sub_result"). There are other parameters but they aren't important (see below).
- Click Query.
- A dialog shows, with a "Filter" text field focused. Type into that field the parts of the benchmark name you want to see that you remember.
- Click "test" in the list box. This causes a second list box to appear.
- Select the specific test from the list box that you care about.
- Refocus the "Filter" text field, and type the name of the specific data point (the sub_result name) you care about.
- Click "sub_result" in the list box.
- Select the specific sub_result that you care about.
- Click "Time Range", then "Date Range".
- Click the calendar icon next to the "Begin" text field. (Don't just type in a new date, because https://bugs.chromium.org/p/skia/issues/detail?id=11279.)
- Select the start date you care about.
- Click "Plot".
You can navigate the X axis of the graph using WASD.
The parameters for a data set are as follows:
sub_result: the specific data stream provided by the test. Tests can provide multiple data points, in a JSON map; each key in that map becomes a sub_result in the Skia Perf system.
branch: the branch that was being tested.
config: always "default".
originId: always "devicelab" except for data that was migrated from the old database, which are labeled "legacy-flutter".
test: the name of the test that ran to collect the data.
unit: in theory, the units in which the data was collected (so each sub_result should only ever be associated with one unit). In practice this parameter is often incorrect.
- Home of the Wiki
- Roadmap
- API Reference (stable)
- API Reference (master)
- Glossary
- Contributor Guide
- Chat on Discord
- Code of Conduct
- Issue triage reports
- Our Values
- Tree hygiene
- Issue hygiene and Triage
- Style guide for Flutter repo
- Project teams
- Contributor access
- What should I work on?
- Running and writing tests
- Release process
- Rolling Dart
- Manual Engine Roll with Breaking Commits
- Updating Material Design Fonts & Icons
- Postmortems
- Setting up the Framework development environment
- The Framework architecture
- The flutter tool
- API Docs code block generation
- Running examples
- Using the Dart analyzer
- The flutter run variants
- Test coverage for package:flutter
- Writing a golden-file test for package:flutter
- Setting up the Engine development environment
- Compiling the engine
- Debugging the engine
- Using Sanitizers with the Flutter Engine
- Testing the engine
- The Engine architecture
- Flutter's modes
- Engine disk footprint
- Comparing AOT Snapshot Sizes
- Custom Flutter engine embedders
- Custom Flutter Engine Embedding in AOT Mode
- Flutter engine operation in AOT Mode
- Engine-specific Service Protocol extensions
- Crashes
- Supporting legacy platforms
- Metal on iOS FAQ
- Engine Clang Tidy Linter
- Why we have a separate engine repo
- Reduce Flutter engine size with MLGO
- Setting up the Plugins development environment
- Setting up the Packages development environment
- Plugins and Packages repository structure
- Plugin Tests
- Contributing to Plugins and Packages
- Releasing a Plugin or Package
- Unexpected Plugins and Packages failures