Speed tweaks for Robust algorithms & make examples faster #77
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
…ustering. Update doc, test, examples. Fix typo
|
Added: cython code for kmeans loss (modified from sklearn implementation), significant speedup for |
TimotheeMathieu
changed the title
TimotheeMathieu
changed the title
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.
Following issue #76 .
I added the same stopping criterion as for sklearn's SGDClassifier/SGDRegressor (i.e. stop if the loss does not change after n_iter_no_change steps). I also sub-sampled the California houses dataset example and clustering example.
Result :
On a recent CPU.
Is it sufficient or should I find examples that are faster to run ?