Nice call out.
So there is precedence on NOT utilizing the Mahout inCore matrix/vector
structure in Mahout Bindings See H2O bindings.
In this case we let the underlying engine (in this case MADlib) utilize
its own concept of a Matrix.
Makes quicker work of writing bindings and, since most of the deep stuff in
MADlib is CPP, I assume there's fairly good performance there anyway.
(Mahout is JVM under the hood, so with out the accelerators, performance
was not spectacular).
Trevor Grant
Data Scientist
https://github.com/rawkintrevo
http://stackexchange.com/users/3002022/rawkintrevo
http://trevorgrant.org
*"Fortunate is he, who is able to know the causes of things." Virgil*
On Sun, May 21, 2017 at 9:05 PM, Jim Nasby <jim.nasby@openscg.com> wrote:
> On 5/21/17 7:38 PM, Trevor Grant wrote:
>
>> I don't think a PhD in math/ML is required at all for this little venture.
>> Mainly just a knowledge of basic BLAS operations (Matrix A %*% Matrix B,
>> Matrix A %*% Vector, etc.)
>>
>
> Related to that, there's also been discussion[1] on the Postgres hackers
> list about adding a true matrix data type. Having that would allow plCUDA
> to do direct GPU matrix math with the bare minimum of fuss.
>
> Madlib would presumably need some other solution for nonpostgres stuff
> (though, the matrix type could potentially be pulled into GPDB with minimal
> fuss).
>
> 1: https://www.postgresql.org/messageid/flat/9A28C8860F777E439
> AA12E8AEA7694F8011F52EF%40BPXM15GP.gisp.nec.co.jp
> 
> Jim Nasby, Chief Data Architect, Austin TX
> OpenSCG http://OpenSCG.com
>
