Optimized Spark recall_at_k time performance #1796
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
ChuyangKe
requested review from
gramhagen,
anargyri,
loomlike and
wutaomsft
as code owners
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.
Description
Optimized time performance of recall_at_k() in Spark evaluation metrics.
The function is tested on the MovieLens 20m dataset with 138,493 users, and with TOP_K = 50 recommendations generated for each user. The time cost of evaluating the recall of the recommendations is reduced from 6.99s to 1.09s, indicating a 7x performance improvement.
Related Issues
Checklist:
staging branchand not tomain branch.