Skip to content

Latest commit

 

History

History
122 lines (89 loc) · 6.68 KB

README.md

File metadata and controls

122 lines (89 loc) · 6.68 KB
Raw

flink-benchmarks

This repository contains sets of micro benchmarks designed to run on single machine to help Apache Flink's developers assess performance implications of their changes.

The main methods defined in the various classes (test cases) are using jmh micro benchmark suite to define runners to execute those test cases. You can execute the default benchmark suite (which takes ~1hour) at once:

mvn clean install exec:exec

There is also a separate benchmark suit for state backend, and you can execute this suit (which takes ~1hour) using below command:

mvn clean package exec:exec \
 -Dbenchmarks="org.apache.flink.state.benchmark.*"

If you want to execute just one benchmark, the best approach is to execute selected main function manually. There're mainly three ways:

  1. From your IDE (hint there is a plugin for Intellij IDEA).

    • In this case don't forget about selecting flink.version, default value for the property is defined in pom.xml.

  2. From command line, using command like:

    mvn -Dflink.version=<FLINK_VERSION> clean package exec:exec \
 -Dbenchmarks="<benchmark_class>"

    An example flink version can be -Dflink.version=1.12-SNAPSHOT.

  3. Run the uber jar directly like:

    java -jar target/benchmarks.jar -rf csv "<benchmark_class>"

We also support to run each benchmark once (with only one fork and one iteration) for testing, with below command:

mvn test -P test

Parameters

There are some built-in parameters to run different benchmarks, these can be shown/overridden from the command line.

# show all the parameters combination for the <benchmark_class> 
java -jar target/benchmarks.jar "<benchmark_class>" -lp

# run benchmark for rocksdb state backend type 
java -jar target/benchmarks.jar "org.apache.flink.state.benchmark.*" -p "backendType=ROCKSDB"

Configuration

Besides the parameters, there is also a benchmark config file benchmark-conf.yaml to tune some basic parameters. For example, we can change the state data dir by putting benchmark.state.data-dir: /data in the config file. For more options, you can refer to the code in the org.apache.flink.config package.

Prerequisites

The recent addition of OpenSSL-based benchmarks require one of two modes to be active:

  • dynamically-linked OpenSSL (default): this uses a dependency with native wrappers that are linked dynamically to your system's libraries. Depending on the installed OpenSSL version and OS, this may fail and you should try the next option:
  • statically-linked OpenSSL: this can be activated by mvn -Dnetty-tcnative.flavor=static but requires flink-shaded-netty-tcnative-static in the version from pom.xml. This module is not provided by Apache Flink by default due to licensing issues (see https://issues.apache.org/jira/browse/LEGAL-393) but can be generated from inside a corresponding flink-shaded source via:
mvn clean install -Pinclude-netty-tcnative-static -pl flink-shaded-netty-tcnative-static

If both options are not working, OpenSSL benchmarks will fail but that should not influence any other benchmarks.

Code structure

To avoid compatibility problems and compilation errors, benchmarks defined in this repository should be using stable @Public Flink API. If this is not possible the benchmarking code should be defined in the Apache Flink repository. In this repository there should be committed only a very thin executor class that's using executing the benchmark. For this latter pattern please take a look for example at the CreateSchedulerBenchmarkExecutor and how is it using CreateSchedulerBenchmark (defined in the flink-runtime). Note that the benchmark class should also be tested, just as CreateSchedulerBenchmarkTest is tested in the flink-runtime.

Such code structured is due to using GPL2 licensed jmh library for the actual execution of the benchmarks. Ideally we would prefer to have all of the code moved to Apache Flink

General remarks

  • If you can not measure the performance difference, then just don't bother (avoid premature optimisations).
  • Make sure that you are not disturbing the benchmarks. While benchmarking, you shouldn't be touching the machine that's running the benchmarks. Scrolling web page in a browser or changing windows (alt/cmd + tab) can seriously affect the results.
  • If in doubt, verify the results more then once, like:
    1. measure the base line
    2. measure the change, for example +5% performance improvement
    3. switch back to the base line, make sure that the result is worse
    4. go back to the change and verify +5% performance improvement
    5. if something doesn't show the results that you were expecting, investigate and don't ignore this! Maybe there is some larger performance instability and your previous results were just lucky/unlucky flukes.
  • Some results can show up over the benchmarking noise only in long term trends.
  • Please tune the length of the benchmark (usually by number of processed records). The less records, the faster the benchmark, the more iterations can be executed, however the higher chance of one of setup overheads skewing the results. Rule of thumb is that you should increase the number of processed records up to a point where results stop improving visibly, while trying to keep the single benchmark invocation under/around 1 second.

Naming convention

Regarding naming the benchmark methods, there is one important thing. When uploading the results to the codespeed web UI, uploader is using just the benchmark's method name combined with the parameters to generate visible name of the benchmark in the UI. Because of that it is important to:

  1. Have the method name explanatory enough so we can quickly recognize what the given benchmark is all about, using just the benchmark's method name.
  2. Be as short as possible to not bloat the web UI (so we must drop all of the redundant suffixes/prefixes, like benchmark, test, ...)
  3. Class name is completely ignored by the uploader.
  4. Method names should be unique across the project.

Good example of how to name benchmark methods are:

  • networkThroughput
  • sessionWindow

Submitting a pull request

Please attach the results of your benchmarks.