Skip to content

Benchmarking UI5 Tooling

For benchmarking UI5 Tooling we typically make use of the open source tool hyperfine.

In general we only benchmark calls to the UI5 CLI. However, we might add scripted benchmarks for some components in the future.

The following is a walk-through on how to evaluate the performance impact of an imaginary change in the UI5 Builder project.


  1. Install hyperfine
  2. Prepare the UI5 Tooling projects you want to measure (optional if your development environment already reflects this):

    1. Start in an empty directory
      mkdir ui5-tooling-benchmark && cd ui5-tooling-benchmark/
    2. Clone UI5 CLI
      git clone
    3. Clone UI5 Builder (or your fork)
      git clone
      Make sure you check out the main branch, since we'll perform the baseline test first
    4. Install npm dependencies in both directories
      (cd ui5-cli && npm install)
      (cd ui5-builder && npm install)
    5. Create global npm links for both projects
      (cd ui5-cli && npm link)
      (cd ui5-builder && npm link)
    6. Link UI5 Builder into UI5 CLI
      (cd ui5-cli && npm link @ui5/builder)
    7. Verify your setup

      ui5 --version
      This should output the version and location of the UI5 CLI you just cloned.

      For example:

      3.0.0 (from /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs)

  3. Prepare your test project (we choose the openui5-sample-app)

    1. Clone the project
      git clone
    2. Navigate into the project
      cd openui5-sample-app
    3. Install any required npm dependencies
      npm install
      Note: We won't link UI5 CLI into this project. Instead, we'll call it directly.
    4. Verify that the previously installed UI5 CLI can be called with the following command:
      UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs --version
      On Windows:
      set UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs --version
      (Replace the path to ui5.cjs with the one shown in the previous ui5 --version output)


  1. Depending on how reliable you'd like the measurements to be, consider preparing your system:

    1. Connect your computer to a power supply
    2. Make sure no updates or anti-virus scans are taking place
    3. Close all applications. This includes your IDE, since it might start indexing any new files created during the build, thus impacting I/O
    4. Don't interact with your system wile the benchmarking is running
  2. Perform the baseline measurement

    1. In the project, start your first benchmark
      hyperfine --warmup 1 \
      'UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs build' \
      --export-markdown ./
      On Windows:
      hyperfine --warmup 1 \
      'set UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs build' \
      --export-markdown ./
    2. Your baseline benchmark is now stored in and should look similar to this:

      Command Mean [s] Min [s] Max [s] Relative
      UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs build 1.439 ± 0.036 1.400 1.507 1.00
  3. Prepare your change

    1. Switch to the branch that contains your change
      (cd ../ui5-builder && git checkout my-change)
    2. If your change requires different npm dependencies, reinstall them
      (cd ../ui5-builder && npm install)
    3. The link from UI5 CLI is still in place. However, if you have changes in multiple UI5 Tooling modules, you might need to npm link those again
  4. Perform the change measurement

    1. In the project, start your second benchmark
      hyperfine --warmup 1 \
      'UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs build' \
      --export-markdown ./
      On Windows:
      hyperfine --warmup 1 \
      'set UI5_CLI_NO_LOCAL=X node /my/home/ui5-tooling-benchmark/ui5-cli/bin/ui5.cjs build' \
      --export-markdown ./
    2. Your change's benchmark is now stored in

Compile Results

  1. Merge both measurements into one markdown

    1. In this setup, Hyperfine can't correctly calculate the relative difference between results. The respective column always reads "1". Either remove the "Relative" column or calculate the relative difference yourself:

      • Use this formula to calculate the percentage increase based on the Mean result:
        (newMean - baselineMean) / baselineMean * 100
        JavaScript function:
        function calcDiff(baseVal, newVal) {return (newVal - baseVal) / baseVal * 100;}

      • Example for a performance improvement:
        Baseline of 10 seconds decreased to 7 seconds:
        (7-10)/10*100 = -30 => -30% change

      • Example for a performance deterioration:
        Baseline of 10 seconds increased to 12 seconds:
        (12-10)/10*100 = 20 => +20% change

    2. Change the unit in the Mean/Min/Max column headers to seconds or milliseconds according to your results.

    3. Change the command column to only contain the relevant ui5 build command, including any parameters. E.g. ui5 build --all
    4. You should end up with a markdown like this:

      ui5-builder Ref | Command | Mean [s] | Min [s] | Max [s] | Relative
      | main ([`1234567`](<sha>)) | `ui5 build` | 1.439 ± 0.036 | 1.400 | 1.507 | Baseline |
      | feature-duck ([`9101112`](<sha>)) | `ui5 build` | 1.584 ± 0.074 | 1.477 | 1.680 | **+10%** |
      Rendering like this:

      ui5-builder Ref Command Mean [s] Min [s] Max [s] Relative
      main (1234567) ui5 build 1.439 ± 0.036 1.400 1.507 Baseline
      feature-duck (9101112) ui5 build 1.584 ± 0.074 1.477 1.680 +10%
  2. You can now share these results on GitHub or wherever you might need them.

Happy benchmarking! 🏎