[
https://issues.apache.org/jira/browse/MAHOUT-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956282#comment-13956282
]
Dmitriy Lyubimov commented on MAHOUT-1500:
------------------------------------------
bq. o.a.m.math.Matrix and Vector API are reserved for in-core operations only,
and all algorithms around it are built assuming "shared memory" model
In particular, to that end, the cost-optimized approach for in-core math vector
operations written by Robin assumes in-core only cost models. It absolutely
isn't compatible with any notion of a distributed vector, and messing with
these cost optimizations is the last thing i'd like to suggest here. Not to
mention outer user block algorithms.
Which is a strong argument as to why those two approaches to cost optimization
(in-core vs. distributed) should really be kept strictly apart in two separate
wards with cotton blankets on the walls and under 24hr monitoring.
> H2O integration
> ---------------
>
> Key: MAHOUT-1500
> URL: https://issues.apache.org/jira/browse/MAHOUT-1500
> Project: Mahout
> Issue Type: Improvement
> Reporter: Anand Avati
> Fix For: 1.0
>
>
> Integration with h2o (github.com/0xdata/h2o) in order to exploit its high
> performance computational abilities.
> Start with providing implementations of AbstractMatrix and AbstractVector,
> and more as we make progress.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
