Performance improvement attempt #1
Open
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.
Congratulations on the article, code and work, incredible method, I'm using it!
I'm not a computer expert, but I saw the opportunity to contribute and speed up calculations. In simple tests, images in examples, I verified a performance gain.
The changes were to the dissimilarity and iteration_no_verbose calculations (in force.execute); name updated to dissimilarity_no_verbose and iteration_no_verbose, respectively, as they don't use tqdm.
Changes: (a) Critical loops have been included in numba functions;
(b) numba cache has been activated to save compilation time;
(c) parallel loops (prange) inside other parallel loops have been removed, replaced by range, avoiding parallelization overload, making parallel the highest demand only.
Previous comments contain test prints comparing the efficiency of the functions.
The functions have not been changed, just reorganized.
I'm happy to help if this has helped. Thank you for your attention.