Add Extensive Tests to Check Benchmarks

Add extensive tests that check if the benchmarks are still performing as expected. These tests should only be executed after big changes or once in a while but not after each commit. Potentially in parallel on the cluster.

The issue names no files, tests, or entry points. Start by locating the benchmark implementations and existing test or execution configuration, then determine how benchmark runs are triggered and what performance expectations can be measured. Done means an occasional, non-per-commit test suite that checks benchmark performance and defines whether parallel cluster execution is supported.

Written by the indexing model from the issue text.