Home of Test Results Summary Service (TRSS) and PerfNext. These tools are designed to improve our ability to monitor and triage tests at the Adoptium project. The code is generic enough that it is extensible for use by any project that needs to monitor multiple CI servers and aggregate their results.
By default (no benchmark filter), Tabular View should show all metrics. As shown in the screenshots below, it doesn't shows only one metric (i.e. footprint) for pingperf-quarkus-startup benchmark and misses the other one (i.e. startup time). When we use the benchmark filter to explicitly selected Quarkus benchmarks or when we use Perf Compare, then we can see both the metrics for pingperf as shown in the screenshots below.
We noticed this issue after #230 was merged and the server was updated with the latest changes.
Observation: Looking at the raw data, the baseline build might have been aborted in its first iteration, while the test build would have been aborted after finishing 3 iterations. This is because builds had to be aborted because of Jenkins overloading. Not sure whether that has anything to do with this issue. Each iteration results in 5 values.
Without Benchmark Filter (Can see only one metric)
piyush286
commented
4 years ago
By default (no benchmark filter), Tabular View should show all metrics. As shown in the screenshots below, it doesn't shows only one metric (i.e. footprint) for
pingperf-quarkus-startupbenchmark and misses the other one (i.e. startup time). When we use the benchmark filter to explicitly selected Quarkus benchmarks or when we use Perf Compare, then we can see both the metrics for pingperf as shown in the screenshots below.We noticed this issue after #230 was merged and the server was updated with the latest changes.
Observation: Looking at the raw data, the baseline build might have been aborted in its first iteration, while the test build would have been aborted after finishing 3 iterations. This is because builds had to be aborted because of Jenkins overloading. Not sure whether that has anything to do with this issue. Each iteration results in 5 values.
Without Benchmark Filter (Can see only one metric)
With Benchmark Filter (Can see both metrics)
Perf Compare (Can see both metrics)