Intel OSPray is a portable ray-tracing engine for high-performance, high-fidelity scientific visualizations. OSPray builds off Intel's Embree and Intel SPMD Program Compiler (ISPC) components as part of the oneAPI rendering toolkit.
To run this test with the Phoronix Test Suite, the basic command is: phoronix-test-suite benchmark ospray.
* 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 25 May 2022.
pts/ospray-2.9.0 [View Source] Fri, 11 Mar 2022 19:49:05 GMT Update against upstream OSPray 2.9.0 release now that ospray-studio works for testing scenes.
OpenBenchmarking.org metrics for this test profile configuration based on 301 public results since 11 March 2022 with the latest data as of 25 May 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 (OSPray 2.9 - Benchmark: gravity_spheres_volume/dim_512/ao/real_time) has an average run-time of 7 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.
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.
Notable Instruction Set Usage
Notable instruction set extensions supported by this test, based on an automatic analysis by the Phoronix Test Suite / OpenBenchmarking.org analytics engine.
Used by default on supported hardware. Found on Intel processors since at least 2010. Found on AMD processors since Bulldozer (2011).
Last automated analysis: 12 March 2022
This test profile binary relies on the shared libraries librt.so.1, libospray.so.2, librkcommon.so.1, libtbb.so.12, libtbbmalloc.so.2, libdl.so.2, libembree3.so.3, libopenvkl.so.1, libm.so.6, libpthread.so.0, libc.so.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.