rays1bench

This is a test of rays1bench, a simple path-tracer / ray-tracing that supports SSE and AVX instructions, multi-threading, and other features. This test profile is measuring the performance of the "large scene" in rays1bench.

To run this test with the Phoronix Test Suite, the basic command is: phoronix-test-suite benchmark rays1bench.

Project Site

github.com

Test Created

9 January 2020

Test Maintainer

Michael Larabel 

Test Type

Processor

Average Install Time

5 Seconds

Average Run Time

1 Minute, 15 Seconds

Test Dependencies

C/C++ Compiler Toolchain + Python

Accolades

10k+ Downloads

Supported Platforms


Public Result Uploads *Reported Installs **Reported Test Completions **Test Profile Page Views ***OpenBenchmarking.orgEventsrays1bench Popularity Statisticspts/rays1bench2020.012020.032020.052020.072020.092020.112021.012021.032021.052021.072021.092021.112022.012022.032022.052022.072022.092022.112023.012023.032023.052023.072023.092023.112024.012024.032024.052024.072024.092024.118001600240032004000
* 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 November 2024.

Revision History

pts/rays1bench-1.0.0   [View Source]   Thu, 09 Jan 2020 18:46:02 GMT
Initial commit of rays1bench path tracer.

Suites Using This Test

Multi-Core

Raytracing

Creator Workloads

Renderers


Performance Metrics

Analyze Test Configuration:

rays1bench 2020-01-09

Large Scene

OpenBenchmarking.org metrics for this test profile configuration based on 1,190 public results since 9 January 2020 with the latest data as of 21 October 2024.

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.

Component
Percentile Rank
# Compatible Public Results
mrays/s (Average)
100th
15
1008 +/- 48
87th
6
374 +/- 35
79th
7
296 +/- 4
77th
7
272 +/- 6
77th
3
269 +/- 2
Mid-Tier
75th
< 253
71st
7
227 +/- 2
69th
16
219 +/- 1
63rd
7
164 +/- 2
61st
3
156 +/- 1
57th
7
117 +/- 1
55th
15
113 +/- 6
53rd
7
109 +/- 1
Median
50th
105
49th
10
99 +/- 1
42nd
14
81 +/- 1
37th
4
68 +/- 5
36th
7
67 +/- 1
28th
4
56 +/- 2
Low-Tier
25th
< 53
23rd
6
50 +/- 3
19th
13
44 +/- 1
12th
5
30 +/- 2
OpenBenchmarking.orgDistribution Of Public Results - Large Scene1190 Results Range From 5 To 1078 mrays/s5387110413717020323626930233536840143446750053356659963266569873176479783086389692996299510281061109460120180240300

Based on OpenBenchmarking.org data, the selected test / test configuration (rays1bench 2020-01-09 - Large Scene) 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.

OpenBenchmarking.orgMinutesTime Required To Complete BenchmarkLarge SceneRun-Time246810Min: 1 / Avg: 1.2 / Max: 5

Based on public OpenBenchmarking.org results, the selected test / test configuration has an average standard deviation of 0.1%.

OpenBenchmarking.orgPercent, Fewer Is BetterAverage Deviation Between RunsLarge SceneDeviation246810Min: 0 / Avg: 0.13 / Max: 2

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.

AMDIntelOpenBenchmarking.orgRelative Core Scaling To Baserays1bench CPU Core ScalingLarge Scene4681012162432486496128918273645

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.

CPU Architecture
Kernel Identifier
Verified On
Intel / AMD x86 64-bit
x86_64
(Many Processors)

Recent Test Results

OpenBenchmarking.org Results Compare

17 Systems - 2641 Benchmark Results

6 Systems - 344 Benchmark Results

AMD Ryzen AI 9 HX 370 - ASUS Zenbook S 16 UM5606WA_UM5606WA UM5606WA v1.0 - AMD Device 1507

Ubuntu 24.10 - 6.11.0-rc6-phx - GNOME Shell

1 System - 1043 Benchmark Results

5 Systems - 531 Benchmark Results

AMD Ryzen 7 5800X 8-Core - ASRock X570 Pro4 - AMD Starship

Ubuntu 22.04 - 5.17.4-051704-generic - GNOME Shell 42.0

1 System - 377 Benchmark Results

AMD Ryzen 7 5800X 8-Core - ASUS ROG STRIX X370-F GAMING - AMD Starship

Linuxmint 21.3 - 6.5.0-35-lowlatency - X Server 1.21.1.4

4 Systems - 84 Benchmark Results

Intel Core i5-14400F - ASUS PRIME Z790-P WIFI - Intel Raptor Lake-S PCH

Ubuntu 24.04 - 6.8.0-31-generic - GNOME Shell 46.0

4 Systems - 86 Benchmark Results

AMD Ryzen 5 8400F 6-Core - ASRock B650 Pro RS - AMD Device 14e8

Ubuntu 24.04 - 6.8.0-31-generic - GNOME Shell 46.0

Find More Test Results