You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Saikat Kanjilal (JIRA)" <ji...@apache.org> on 2010/09/23 17:56:33 UTC

[jira] Commented: (MAHOUT-319) SVD solvers should be gracefully stoppable/restartable

    [ https://issues.apache.org/jira/browse/MAHOUT-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914069#action_12914069 ] 

Saikat Kanjilal commented on MAHOUT-319:
----------------------------------------

I would like to help out on this task by building  a notion of persisting of the state generically to fix this and build implementations of an RDBMS, local disk or HDFS underneath.   Let me know if thats ok with you guys.  Out of curiosity when is 0.5 planned to be released?

> SVD solvers should be gracefully stoppable/restartable
> ------------------------------------------------------
>
>                 Key: MAHOUT-319
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-319
>             Project: Mahout
>          Issue Type: Improvement
>    Affects Versions: 0.3
>            Reporter: Jake Mannix
>            Assignee: Jake Mannix
>             Fix For: 0.5
>
>
> LanczosSolver, DistributedLanczosSolver, and HebbianSolver all keep copious amounts of memory-resident data which is lost if the app crashes or is killed (OOM, forgetting to run in a screen session, and losing net connectivity to the server running it, etc...).  
> These algorithms (and many other Mahout processes!) should enable a pluggable "persist state" mechanism (to HDFS, RDBMS, local disk, key-value store, etc), and similarly, a way to pick up and start from such a state.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.