diff options
| author | James Barnett <noreply@jamesbarnett.xyz> | 2025-07-31 18:16:10 +0100 |
|---|---|---|
| committer | James Barnett <noreply@jamesbarnett.xyz> | 2025-07-31 18:16:10 +0100 |
| commit | abe1f21f84df5864e8a7781864d9e32436bde2d4 (patch) | |
| tree | e2b8100bc9e6523db4ade4746d98bd33d1ead513 /README.md | |
| parent | bccbcc12c72f5edde605601a311646d1ca96d7e1 (diff) | |
| download | js-raytracer-abe1f21f84df5864e8a7781864d9e32436bde2d4.tar.xz js-raytracer-abe1f21f84df5864e8a7781864d9e32436bde2d4.zip | |
Add more reference benchmark scores. Update readme
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -10,6 +10,16 @@ No graphics APIs or libraries are used, only a single HTML5 canvas call to draw Various effects are supported, including recursive optical reflections and refractions, and [Phong shading](https://en.wikipedia.org/wiki/Phong_reflection_model). Basic multi-threading is implemented using the [Web Workers API](https://developer.mozilla.org/en-US/docs/Web/API/). +## Benchmarking +The raytracer can also be used as a basic CPU performance benchmarking tool. + +This will test the JavaScript execution performance of your CPU and web browser, and provide a raytracing throughput score in pixels per millisecond. + +I've run the benchmark on various different devices I have access to, which provide some reference scores for comparison. +View them on the [benchmarking page](https://jamesbarnett.io/raytracer#benchmark) and try your own device to see how it compares. + +The JavaScript execution engine your browser used will influence the results. The reference benchmark scores were all run in V8 (Chromium), as unfortunately SpiderMonkey (Firefox) seems to be considerably slower, at least at this specific task. + ## Building locally You will need NodeJS >= 10. |