[go: nahoru, domu]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update instructions for running benchmarks #277

Merged
merged 1 commit into from
Nov 10, 2015
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 11 additions & 8 deletions packages/unit/benchmark/README.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,16 @@
Benchmarks
==========
# Benchmarks

This directory (and its sub-directories) contain benchmarks for Flutter.
The reporting format for benchmarks is not standardized yet, so benchmarks
here are typically run by hand. To run a particular benchmark, use a command
similar to that used to run individual unit tests. For example:
here are typically run by hand. To run a benchmark:

1. Build `sky_shell` for Linux Release using the instructions in the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm surprised we haven't renamed it cocoon or something by now. :p

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, the binaries still need new names.

[Engine repository](https://github.com/flutter/engine).

2. Run `pub get` in the `packages/unit` directory.

3. Run the benchmark:

```
sky/tools/run_tests --debug -r expanded benchmark/gestures/velocity_tracker_bench.dart
/path/to/engine/src/out/Release/sky_shell packages/unit/benchmark/stocks/layout_bench.dart --package-root=packages/unit/package
```

(The `-r expanded` flag prints one line per test, which can be more helpful
than the default format when running individual tests.)