[
https://issues.apache.org/jira/browse/MAHOUT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164352#comment-13164352
]
Sean Owen commented on MAHOUT-910:
----------------------------------
Yes, you would just set a very high value for the first and third limits, and
set your desired limit for the second one. I think it's a superset of the
original implementation and yours.
It occurs to me we need a reliable way to specify "no limit". And you're using
log base 2 instead of e, which maybe makes more sense. Why don't I bake those
two ideas in -- then I think it's the same thing?
> Improve sampling in SamplingCandidateItemStrategy, optimize intersection
> computations
> -------------------------------------------------------------------------------------
>
> Key: MAHOUT-910
> URL: https://issues.apache.org/jira/browse/MAHOUT-910
> Project: Mahout
> Issue Type: Improvement
> Components: Collaborative Filtering
> Affects Versions: 0.5
> Reporter: Sean Owen
> Assignee: Sean Owen
> Fix For: 0.6
>
> Attachments: MAHOUT-910.patch, MAHOUT-910.patch, MAHOUT-910.patch,
> SamplingCandidateItemsStrategy.java
>
>
> Per the lengthy discussion on the mailing list about optimizing
> SamplingCandidateItemStrategy and related code, I'm opening this placeholder
> issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
