Skip to content

README: the ray tracer's 2026-10-31 results - #781

Merged
ASDAlexander77 merged 1 commit into
mainfrom
readme-performance-2026-10-31
Nov 8, 2026
Merged

ASDAlexander77 merged 1 commit into
mainfrom
readme-performance-2026-10-31

Conversation

@ASDAlexander77

@ASDAlexander77 ASDAlexander77 commented Nov 8, 2026 •

Copy link
Copy Markdown
Owner

The README's Performance section still showed the 2026-10-21 ray tracer numbers (gc 1298 ms, "26x slower" than C++). tslang/benchmarks/raytrace/README.md has had the 2026-10-31 results for a while; this brings the README in line with it.

  • The table now gives gc 71, none 70, own 77 and rc 110 ms, 1.3–2.0x of idiomatic Rust (55 ms).
  • It says the benchmark's copy uses @value types, which a reader needs in order to read the numbers fairly.
  • The Rust and C++ rows are still the 2026-10-21 runs on the same machine, and the text says so.
  • One short paragraph explains what changed since 2026-10-21 and points to the benchmark README for every step.

Prompted by the follow-up on discussion #163, which quotes the same numbers.

Docs only; no code changed.

🤖 Generated with Claude Code

The Performance table still gave the 2026-10-21 numbers (gc 1298 ms,
26x slower than C++). Since then @value, parameters captured by copy,
direct calls and tagless null took the tslang builds to 70-110 ms,
1.3-2.0x of idiomatic Rust; the table now gives those, as
tslang/benchmarks/raytrace/README.md does.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ASDAlexander77
ASDAlexander77 merged commit 39922f0 into main Nov 8, 2026
2 checks passed
@ASDAlexander77
ASDAlexander77 deleted the readme-performance-2026-10-31 branch November 8, 2026 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant