Performance improvements: Add @inbounds optimization for ~43% RHS speedup #30
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.
Summary
@inboundsannotations to generated RHS code loops for ~43% speedupPerformance Benchmarks
RHS Evaluation (Telegraph model, 2x21x81 state space):
Index Iteration:
singleindices: 0 allocationspairedindices: 0 allocationsChanges
src/build_rhs.jl@inboundsto the first pass loop (singleindices iteration)@inboundsto the second pass loops (pairedindices iteration)src/build_rhs_ss.jl@inboundsto the steady-state single pass loopsrc/matrix.jl@inboundsto sparse matrix construction loopstest/alloc_tests.jl(new)The
@inboundsoptimization is safe because:singleindicesreturnsCartesianIndiceswhich are guaranteed validpairedindicesreturns index pairs computed to be within boundsTest Plan
cc @ChrisRackauckas
🤖 Generated with Claude Code