This is a test of Kvazaar as a CPU-based H.265/HEVC video encoder written in the C programming language and optimized in Assembly. Kvazaar is the winner of the 2016 ACM Open-Source Software Competition and developed at the Ultra Video Group, Tampere University, Finland.
To run this test with the Phoronix Test Suite, the basic command is: phoronix-test-suite benchmark kvazaar.
* Uploading of benchmark result data to OpenBenchmarking.org is always optional (opt-in) via the Phoronix Test Suite for users wishing to share their results publicly. ** Data based on those opting to upload their test results to OpenBenchmarking.org and users enabling the opt-in anonymous statistics reporting while running benchmarks from an Internet-connected platform. *** Test profile page view reporting began March 2021. Data updated weekly as of 21 April 2024.
Revision History
pts/kvazaar-1.2.0 [View Source] Wed, 04 Jan 2023 10:52:55 GMT Update against Kvazaar 2.2 upstream.
pts/kvazaar-1.1.1 [View Source] Sun, 12 Dec 2021 19:24:06 GMT Fix for filename collision on Windows.
pts/kvazaar-1.1.0 [View Source] Wed, 13 Oct 2021 09:21:18 GMT Update against upstream kvazaar 2.1, has some performance optimizations.
pts/kvazaar-1.0.0 [View Source] Fri, 16 Oct 2020 18:33:23 GMT Initial commit of Kvazaar H.265 video encoder benchmark.
Video Input: Bosphorus 1080p - Video Preset: Medium
OpenBenchmarking.org metrics for this test profile configuration based on 1,005 public results since 16 October 2020 with the latest data as of 21 March 2023.
Below is an overview of the generalized performance for components where there is sufficient statistically significant data based upon user-uploaded results. It is important to keep in mind particularly in the Linux/open-source space there can be vastly different OS configurations, with this overview intended to offer just general guidance as to the performance expectations.
Based on OpenBenchmarking.org data, the selected test / test configuration (Kvazaar 2.0 - Video Input: Bosphorus 1080p - Video Preset: Medium) has an average run-time of 4 minutes. By default this test profile is set to run at least 3 times but may increase if the standard deviation exceeds pre-defined defaults or other calculations deem additional runs necessary for greater statistical accuracy of the result.
Based on public OpenBenchmarking.org results, the selected test / test configuration has an average standard deviation of 0.1%.
Does It Scale Well With Increasing Cores?
Yes, based on the automated analysis of the collected public benchmark data, this test / test settings does generally scale well with increasing CPU core counts. Data based on publicly available results for this test / test settings, separated by vendor, result divided by the reference CPU clock speed, grouped by matching physical CPU core count, and normalized against the smallest core count tested from each vendor for each CPU having a sufficient number of test samples and statistically significant data.
Tested CPU Architectures
This benchmark has been successfully tested on the below mentioned architectures. The CPU architectures listed is where successful OpenBenchmarking.org result uploads occurred, namely for helping to determine if a given test is compatible with various alternative CPU architectures.
