3 ms·
Adam, sorry guess I was not clear. What I said was that the MS Sql server + R strategy of baking in ML in PLSQL is appalling and doing something like what you a
by deepGem 9y ago
Adam, sorry guess I was not clear. What I said was that the MS Sql server + R strategy of baking in ML in PLSQL is appalling and doing something like what you are doing with DL4J is perhaps the right approach.
The multi GPU support rant was for SQL Server + R, not DL4J.
"You've also for some reason decided to attach an open ended coding library where you can do whatever you want to a database?"
I didn't catch this part.
- agibsonccc 9y agoRight so I think we were agreeing that how database servers bake in the ML is a bit weird and not the way to go. The "open ended coding library" is datavec here. Comparing them here is only really semi valid. The processes there are definitely brittle.