Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(225)

Side by Side Diff: pkg/analysis_server/benchmark/integration/README.md

Issue 1244023003: performance measurement readme (Closed) Base URL: git@github.com:dart-lang/sdk.git@master
Patch Set: Created 5 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 # Running Benchmarks
2
3 There are two entry points for running benchmarks:
4 * **main.dart** - a general Dart application for running performance benchmarks
5 * **local_runner.dart** - an example Dart application
6 which sets up the local environment
7 and then calls main.dart to run performance benchmarks
8
9 ## local_runner.dart
10
11 This Dart application is one example for running performance benchmarks.
12 When run, this application 1) extracts a branch from a git repository
13 into a temporary directory, and 2) creates a symlink to the out or xcodebuild
14 directory for proper package-root package resolution.
15 The required command line arguments are
16 * **gitDir** = a path to the git repository containing the initial target source
17 * **branch** = the branch containing the initial target source
18 * **inputFile** = the instrumentation or log file
19
20 Once setup is complete, this applications calls main.dart
21
22 ## main.dart
23
24 This Dart application reads an instrumentation or local log file produced by
25 analysis server, "replays" that interaction with the analysis server,
26 compares the notifications and responses with what was recorded in the log,
27 and produces a report. It assumes that the environment for playback has
28 already been setup.
29 The required command line arguments are
30 * **-i, --input <filePath>**
31 The input file specifying how this client should interact with the server.
32 If the input file name is "stdin", then the instructions are read from stdin.
33 * **-m, --map <oldSrcPath>,<newSrcPath>**
34 This option defines a mapping from the original source directory <oldSrcPath>
35 when the instrumentation or log file was generated
36 to the target source directory <newSrcPath> used during performance testing.
37 Multiple mappings can be specified.
38 WARNING: The contents of the target directory will be modified
39 * **-t, --tmpSrcDir <dirPath>**
40 The temporary directory containing source used during performance measurement.
41 WARNING: The contents of the target directory will be modified
42 * **--newTaskModel** enable the use of the new task model
43 * **-d, --diagnosticPort** localhost port on which server
44 will provide diagnostic web pages
45 * **-v, --verbose** Verbose logging
46 * **--vv** Extra verbose logging
47 * **-h, --help** Print this help information
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698