You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Robin Anil (JIRA)" <ji...@apache.org> on 2010/03/03 06:05:28 UTC
[jira] Issue Comment Edited: (MAHOUT-317) Collocations: Eliminate
in-memory frequency calculation
[ https://issues.apache.org/jira/browse/MAHOUT-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840456#action_12840456 ]
Robin Anil edited comment on MAHOUT-317 at 3/3/10 5:05 AM:
-----------------------------------------------------------
The increase in size was because minSupport pruning wasnt there. I added it. Still at the same setting the output seems a bit different from the earlier one. (some hundred words more @ ~1.2MB dictionary size)
The spill thread problem is still there
was (Author: robinanil):
The increase in size was because minSupport pruning wasnt there. I added it. Still at the same setting the output seems a bit different from the earlier one. (some hundred words more @ ~1.2 dictionary size)
The spill thread problem is still there
> Collocations: Eliminate in-memory frequency calculation
> -------------------------------------------------------
>
> Key: MAHOUT-317
> URL: https://issues.apache.org/jira/browse/MAHOUT-317
> Project: Mahout
> Issue Type: Improvement
> Affects Versions: 0.3
> Reporter: Drew Farris
> Fix For: 0.3
>
> Attachments: MAHOUT-317.patch, MAHOUT-317.patch, MAHOUT-317.patch
>
>
> see: http://www.lucidimagination.com/search/document/ae484d53e969250e/who_owns_mahout_bucket_on_s3
> The collocation code currently uses maps in the CollocCombiner and CollocReducer to perform frequency calculations which can cause the process to exceed the heap space if a large number of ngrams exist for any given subgram.
> Convert the code to use a composite key / secondary sort to avoid the need for in-memory map for frequency calculations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.