Repository navigation
skill(faer-optimization): parallel splits must scale past the development host - #96
Merged
Merged
Conversation
…ment host 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.
Adds a Parallel splits must scale section to the faer-optimization skill. It points at the common Parallel Scaling rule (tensor4all/tensor4all-agent-rules#28) and lists the traps seen in this fork: a column split that re-reads the whole basis per task (#90), a row split with one partial per thread and a serial combine, and constant task caps or thresholds tuned at one thread count. Scaling evidence must include 1, 8 and the largest thread count on a many-core host (broccoli, 64 cores), with the OpenBLAS arm.
🤖 Generated with Claude Code