benchmark_runner 0.1.2

A library for writing inline micro-benchmarks, reporting score statistics, and running sync/async benchmarks.

Benchmark Runner

Introduction

Benchmarking is used to estimate and compare the execution speed of numerical algorithms and programs. The package benchmark_runner is based on benchmark_harness and includes helper functions for writing inline micro-benchmarks with the option of printing a score histogram and reporting the score mean, standard deviation, median, and inter quartile range.

The benchmark runner allows executing several benchmark files and reports if uncaught exceptions/errors were encountered.

Usage

Include benchmark_runner as a dev_dependency in your pubspec.yaml file.

Write inline benchmarks using the functions:

• benchmark: Creates and runs a synchronous benchmark and reports the benchmark score.
• asyncBenchmark: Creates and runs an asynchronous benchmark.
• group: Used to label a group of benchmarks. The callback body usually contains one or several calls to benchmark and asyncBenchmark. Benchmark groups may not be nested.
• Benchmark files must end with _benchmark.dart in order to be detected by the benchmark_runner.

The example below shows a benchmark file containing synchronous and asynchronous benchmarks.

// ignore_for_file: unused_local_variable

import 'package:benchmark_runner/benchmark_runner.dart';

/// Returns the value [t] after waiting for [duration].
Future<T> later<T>(T t, [Duration duration = Duration.zero]) {
  return Future.delayed(duration, () => t);
}

void main(List<String> args) async {
  await group('Wait for duration', () async {
    await asyncBenchmark('10ms', () async {
      await later<int>(39, Duration(milliseconds: 10));
    });

    await asyncBenchmark('5ms', () async {
      await later<int>(27, Duration(milliseconds: 5));
    }, emitStats: false);
  });

  group('Set', () async {
    await asyncBenchmark('error test', () {
      throw ('Thrown in benchmark.');
    });

    benchmark('construct', () {
      final set = {for (var i = 0; i < 1000; ++i) i};
    });

    throw 'Error in group';
  });
}

1. Running a Single Benchmark File

A single benchmark file may be run as a Dart executable:

$ dart benchmark/example_async_benchmark.dart

The console output is shown above. The following colours and coding are used:

• The first column shows the micro-benchmark runtime.
• The labels of asynchronous benchmarks and groups are marked with an hour-glass symbol.
• The mean and the histogram block containing the mean are printed using green foreground.
• The median and the block containg the median are printed using blue foreground.
• If the same block contains mean and median it is printed using cyan foreground.
• Errors are printed using red foreground.

2. Running Several Benchmark Files

To run several benchmark files (ending with _benchmark.dart) invoke the benchmark_runner and specify a directory. If no directory or file name is specified, then it defaults to benchmark:

$ dart run benchmark_runner

A typical console output is shown above. In this example, the benchmark_runner detected two benchmark files, ran the micro-benchmarks and produced a report.

• The summary shows the total number of completed benchmarks, the number of benchmarks with errors and the number of groups with errors (that do not occur within the scope of a benchmark function).
• To show a stack trace for each error, run the benchmar_runner using the option -v or --verbose.
• The total benchmark run time may be shorter than the sum of the micro-benchmark run times since by default async benchmarks are run in a separate isolate.

Tips and Tricks

• The scores reported by benchmark and asyncBenchmark refer to a single run of the benchmarked function.

• Benchmarks do not need to be enclosed by a group.

• A benchmark group may not contain another benchmark group.

• The program does not check for group description and benchmark description clashes. It can be useful to have a second benchmark with the same name for example to compare the standard score as reported by benchmark_harness and the score statistics.

• By default, benchmark and asyncBenchmark report score statistics. In order to generate the report provided by benchmark_harness use the optional argument emitStats: false.

• Color output can be switched off by using the option: --isMonochrome when calling the benchmark runner. When executing a single benchmark file the corresponding option is --define=isMonochrome=true.

• The default colors used to style benchmark reports are best suited for a dark terminal background. They can, however, be altered by setting the static variables defined by the class ColorProfile. In the example below, the styling of error messages and the mean value is altered.

  import 'package:ansi_modifier/ansi_modifier.dart';
  import 'package:benchmark_runner/benchmark_runner.dart';
  
  void customColorProfile() {
    ColorProfile.error = Ansi.red + Ansi.bold;
    ColorProfile.mean = Ansi.green + Ansi.italic;
  }
  
  void main(List<String> args) {
    // Call function to apply the new custom color profile.
    customProfile();
  }
  

• When running asynchronous benchmarks, the scores are printed in order of completion. The print the scores in sequential order (as they are listed in the benchmark executable) it is required to await the completion of the async benchmark functions and the enclosing group.

Score Sampling

In order to calculate benchmark score statistics a sample of scores is required. The question is how to generate the score sample while minimizing systematic errors (like overheads) and keeping the benchmark run times within acceptable limits.

The graph below shows the strategy currently used:

The sample size is calculated depending on the execution time estimated for a single run.

For short run times below 100000 clock ticks each sample score is generated using the functions measure or measureAsync. The parameter ticks used when calling the functions measure and measureAsync is chosen such that the benchmark score is averaged over:

• ticks < 1000 => 200 runs,
• 1000 < ticks < 1e4 => 200 ... 100 runs (exponentialy interpolated),
• 1e4 < ticks < 1e5 => 100 ... 1 runs,
• ticks > 1e5 => No preliminary averaging of sample scores.

Contributions

Help and enhancement requests are welcome. Please file requests via the issue tracker.

The To-Do list currently includes:

• Add tests.

• Add color profiles optimized for terminals with light background color.

• Improve the way benchmark score samples are generated.

Features and bugs

Please file feature requests and bugs at the issue tracker.