* 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 19 September 2023.
Revision History
windows/redis-1.0.1 [View Source] Fri, 02 Mar 2018 13:58:10 GMT Increase the count size to let the Redis Windows test run longer.
windows/redis-1.0.0 [View Source] Fri, 02 Mar 2018 13:47:48 GMT Add a test profile offering Microsoft MSOpenTech (older) port of Redis for Windows.
Performance Metrics
Analyze Test Configuration:
Redis 3.2.1
Test: SET
OpenBenchmarking.org metrics for this test profile configuration based on 290 public results since 2 March 2018 with the latest data as of 9 October 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 (Redis 3.2.1 - Test: SET) has an average run-time of 5 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.6%.
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.