Draft
Conversation
… version shows no benefit
…since benchmarks show parallelizing one step but not the other isn't beneficial
…rleaving template
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #95 +/- ##
=======================================
Coverage 99.79% 99.79%
=======================================
Files 8 8
Lines 1441 1471 +30
=======================================
+ Hits 1438 1468 +30
Misses 3 3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Draft
…macro boilerplate
This was referenced Mar 27, 2026
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.
Addresses #93
WIP. Works but needs tuning for parallelism to switch on/off at a given size. I don't think there's a way around measuring how each approach performs at runtime because there isn't a portable way to get cache information and there's a very sudden switch from single-threaded to multi-threaded being beneficial as we leave the cache and hit the memory wall.
There's also a very sudden transition from out-of-place being faster to in-place being faster as we leave the cache on Zen4, but Apple M4 is not affected by that and keeps out-of-place performance almost unchanged far past the advertised cache size. That is a rather surprising result.