Speedup _cg_couple_sparse a bit
#330
Merged
Conversation
This file contains 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
|
Here is a pre-built version of the code in this pull request: wheels.zip, you can install it locally by unzipping |
Moving the mu dimension first means that individual iterations store data close together in memory
Luthaf
force-pushed
the
faster-cg-sparse
branch
from
ce196a8 to
dfbfaf1
Compare
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.
Moving the mu dimension first means that individual iterations store data close together in memory.
This makes a test with EquivariantPowerSpectrum from #329 go from 1.8s to 1.1s on my machine. Still horribly slow overall, but a step in the right direction.
📚 Documentation preview 📚: https://rascaline--330.org.readthedocs.build/en/330/