README: correct benchmarks to use KLU as the honest baseline#3
Merged
Conversation
The prior numbers (a) compared against UMFPACK/dense, which fill or scale O(n^3) on the dense-row structure, overstating the advantage, and (b) included a benchmark bug that timed a dense n-by-n U*V formation as if it were re-KLU (the bogus ~785x/~650x figures). KLU's BTF+AMD isolates a few dense rows, so it is the honest sparse baseline: measured, Woodbury is ~1.7x faster on factor+solve and ~3x on the fixed-S reuse path at r=8 (the gap grows with the border width r). UMFPACK fills on the dense rows (~120x slower); dense is O(n^3). Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Corrects the README benchmarks per the analysis in our discussion:
S + U·Vwell and is the honest sparse comparison. Measured (n=5000, r=8): Woodbury 2.9 ms vs KLU 4.9 ms (~1.7×) on factor+solve, and 1.0 ms vs 3.0 ms (~3×) on the fixed-Sreuse path. The advantage grows with the border widthr.n×nU*Vintermediate every iteration — it was timing dense-matrix formation, not re-KLU.O(n³)(~280×).Docs-only. 🤖 Generated with Claude Code