[
https://issues.apache.org/jira/browse/MAHOUT-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661978#comment-13661978
]
Suneel Marthi commented on MAHOUT-1219:
---------------------------------------
Hudson reported this issue.
https://builds.apache.org/job/Mahout-Quality/2006/testReport/junit/org.apache.mahout.clustering.streaming.cluster/StreamingKMeansTest/testClustering_2_/
{Code}
Error Message
Maximum weight too large 0.9718405659036213
Stacktrace
java.lang.AssertionError: Maximum weight too large 0.9718405659036213
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at
org.apache.mahout.clustering.streaming.cluster.StreamingKMeansTest.testClustering(StreamingKMeansTest.java:139)
Standard Output
k log n = 704
org.apache.mahout.math.neighborhood.LocalitySensitiveHashSearch
org.apache.mahout.common.distance.SquaredEuclideanDistanceMeasure
Total number of clusters 1110
Weights: 65536.000000 65536.000000
{Code}
> LSHSearcher not always faster than BruteSearcher
> ------------------------------------------------
>
> Key: MAHOUT-1219
> URL: https://issues.apache.org/jira/browse/MAHOUT-1219
> Project: Mahout
> Issue Type: Test
> Affects Versions: 0.8
> Reporter: Dan Filimon
> Priority: Minor
>
> This is a known issue and the performance of LocalitySensitiveHashSearch
> needs to be further investigated.
> Currently, the one "benchmark" that does this, SearchQualityTest is too
> variable to be informative.
> So, I'm removing LSHSearcher from SearchQualityTest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
