Optimize permutations
with low effort (no change in algorithm)
#184
+12
−10
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.
Code changes
The modifications to the code stem from the following observations.
Observations
for
loop is inefficient.state[i] <= max
is satisfied.@inbounds
.Fixing these leads to an overall 2−6x speed-up of iterating through all permutations (see benchmarks).
Remarks
Observation (1) can be addressed alternatively by rewriting the
for
loop asObservation (2) can be addressed alternatively by replacing the old
if
statement withSince I want to address both (1) and (2), I believe the code becomes simpler if we replace the
for
loop with awhile
loop.Simple benchmark
Benchmark code
Before
After
Discussion
This optimization is a very low hanging fruit and I believe it can be merged without much thought as a short-term nicety to have. See #186 instead for a more substantial improvement, obtained by rewriting
permutations
in terms ofmultiset_permutations
. A broader discussion of the efficiency ofpermutations
is in #185.