Repository navigation
landing: single-core NumPy figures replace the multicore claims - #90
Merged
Merged
Conversation
…darray/ndarray#118) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…against Go) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The landing's speed claims were multicore figures: "2.3–4.5×" on Sum/Mean/Max on 16 cores, and "3.7–5.9×" over one-thread OpenBLAS with multicore Go. The first single-core measurement of the whole API against NumPy 2.5.4 (go-ndarray/ndarray v0.41.0, tracked in go-ndarray/ndarray#118 by cause) contradicts them:
Maxtakes 1.13× NumPy's time on one core;MatMulat 128² takes 1.15×;This PR changes the stats, the lead paragraph and the closing band to state the single-core result:
The figures are copied from
docs/perf-table.mdof go-ndarray/ndarray#119. This should merge after that PR and the ndarray release that carries the table, so the "performance page" link shows the same numbers.landingkit check publicpasses.Refs go-ndarray/ndarray#118, Refs go-ndarray/ndarray#119
🤖 Generated with Claude Code