Add UnitVector tensor refinement - #9515
Performance Gate Passed
⚠️ Unknown Walltime execution environment detected
Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.
For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.
⚡ 2 improved benchmarks
✅ 1536 untouched benchmarks
⏩ 872 skipped benchmarks1
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | Simulation | take[duplicates/repeated/primitive/nonnull/chunks=16/indices=1000] |
270.2 µs | 228.9 µs | +18.07% |
| ⚡ | WallTime | words_gather_scalar[65536] |
9.4 µs | 8.3 µs | +13.46% |
Tip
Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ct/unit-vector-refinement (b1fb0a4) with ct/norm-compute-mode (4c3a203)2
Footnotes
-
872 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
-
No successful run was found on
ct/norm-compute-mode(76656f1) during the generation of this report, so 1d57c92 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩