* 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 current as of 26 November 2022.
pts/network-loopback-1.0.3 [View Source] Fri, 07 Sep 2018 09:48:45 GMT Add nc as a listed SystemDependencies for ex dep handling/
pts/network-loopback-1.0.1 [View Source] Sun, 16 Feb 2014 00:19:45 GMT Workaround potential hang in network-loopback.
pts/network-loopback-1.0.0 [View Source] Mon, 06 Dec 2010 14:58:23 GMT Initial import into OpenBenchmarking.org
Analyze Test Configuration:
Loopback TCP Network Performance
Time To Transfer 10GB Via Loopback
OpenBenchmarking.org metrics for this test profile configuration based on 10,372 public results since 26 February 2011 with the latest data as of 30 November 2022.
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 (Loopback TCP Network Performance - Time To Transfer 10GB Via Loopback) has an average run-time of 2 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.9%.
Does It Scale Well With Increasing Cores?
No, based on the automated analysis of the collected public benchmark data, this test / test settings does not 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.