Yeah point taken from @Dmitriy and @Trevor, the ability is great and will be 
needed some day soon (Spark is especially troublesome in some apps). However 
the existing compute engines code seems of dubious value.

Completely agree with flexible solvers extremely important and yes, we should 
flog the hell out of it. This includes BLAS and future improvements to that 
layer as well as GPUs. Super important.

I also like your taxonomy.

On Mar 24, 2017, at 9:43 AM, Trevor Grant <trevor.d.gr...@gmail.com> wrote:

To date we have referred to the GPU/CPU/CUDA as 'pluggable native-solvers'.
'plugable backends' are the Spark - Flink -H20- whatever.

With the advent of both, I could see the confusion and we may want to
rethink the naming as part of of this too.

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 Fri, Mar 24, 2017 at 11:15 AM, Nikolai Sakharnykh <nsakharn...@nvidia.com
> wrote:

> I guess we might have different interpretation of a backend. So just to
> avoid any confusion in my world (coming from accelerating applications on
> GPUs) the backends would be CUDA, OpenCL, OpenMP and JVM. I think it
> definitely makes sense to advertise GPU support on the front page, along
> with JVM and/or OpenMP for CPUs.
> 
> -----Original Message-----
> From: Suneel Marthi [mailto:smar...@apache.org]
> Sent: Friday, March 24, 2017 11:13 AM
> To: mahout <d...@mahout.apache.org>
> Cc: user@mahout.apache.org
> Subject: Re: Marketing
> 
> On Fri, Mar 24, 2017 at 12:09 PM, Dmitriy Lyubimov <dlie...@gmail.com>
> wrote:
> 
>> On Fri, Mar 24, 2017 at 8:27 AM, Pat Ferrel <p...@occamsmachete.com>
> wrote:
>> 
>>> The multiple backend support is such a waste of time IMO. The DSL
>>> and GPU support is super important and should be made even more
>>> distributed. The current (as I understand it) single threaded GPU
>>> per VM is only the first step in what will make Mahout important for a
> long time to come.
>>> 
>> 
>> This seems self contradicting a bit. Multiple backends is the only
>> thing that remedies it for me. By that i mean both distributed (i/o)
>> backends and the in-memory.
>> 
>> Good CPU and GPU plugins will be important, as well as communication
>> layer alternatives to spark. Spark is not working out well for
>> interconnected problems, and H20 and Flink, well, I'd just forget
>> about them. I'd certainly drop H20 for now.
> 
> 
> FWIW, the H2O backend is more stable than the F%*&k backend, best to drop
> both.
> 
> 
> 
>> But ability to plug in new communication backend primitives seems to
>> be critical in my experience, as well as variety of cpu/gpu chipset
>> support. (I do use both in-memory and i/o custom backends that IMO are
>> a must).
>> 
>> In that sense, it is super-important that custom backends are easy to
>> plug (even if you are absolutely legitimately dissatisfied with the
>> existing ones).
>> 
>> 
>>> Think of Mahout in 5 years what will be important? H2O? Hadoop
> Mapreduce?
>>> Flink? I’ll stake my dollar on no. GPUs yes and up the stakes.
>>> Streaming online learning (kappa style) yes but not sure Mahout is
>>> made for this right now.
>>> 
>>> Or if we are talking about web site revamp +1, I’d be happy to
>>> upgrade my section and have only held off waiting to see a redesign
>>> or moving to Jekyll.
>>> 
>>> As to a new mascot, ok, but the old one fits the name. We tried
>> sub-naming
>>> Mahout-Samsara to symbolize the changing nature and rebirth of the
>> project,
>>> maybe we should drop the name Mahout altogether. the name Mahout,
>>> like
>> the
>>> blue man, is not relevant to the project anymore and maybe renaming,
>>> is good for marketing.
>>> 
>>> On Mar 24, 2017, at 7:37 AM, Nikolai Sakharnykh
>>> <nsakharn...@nvidia.com>
>>> wrote:
>>> 
>>> Agree that the website feels outdated. I would add Samsara code
>>> example
>> on
>>> the front page, list of key algorithms implemented, supported
>>> backends, github & download links, and cut down the news part
>>> especially towards
>> the
>>> end with flat release numbers and dates. Also probably reorganize
>>> the
>> tabs.
>>> 
>>> If we go with honey badger as a mascot do we have any ideas on the
>>> logo itself? Honey badger biting/eating a snake?)
>>> 
>>> -----Original Message-----
>>> From: Trevor Grant [mailto:trevor.d.gr...@gmail.com]
>>> Sent: Thursday, March 23, 2017 8:53 PM
>>> To: d...@mahout.apache.org
>>> Cc: user@mahout.apache.org
>>> Subject: Re: Marketing
>>> 
>>> A student once asked his teacher, "Master, what is enlightenment?"
>>> 
>>> The master replied, "When hungry, eat. When tired, sleep."
>>> 
>>> Sounds like the honey badger to me...
>>> 
>>> 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 Thu, Mar 23, 2017 at 5:43 PM, Pat Ferrel <p...@occamsmachete.com>
>> wrote:
>>> 
>>>> The little blue man (the mahout) was reborn (samsara) as a
>> honey-badger?
>>>> He must be close indeed to reaching true enlightenment, or is that
>>> Buddhism?
>>>> 
>>>> 
>>>> On Mar 23, 2017, at 12:42 PM, Andrew Palumbo <ap....@outlook.com>
>> wrote:
>>>> 
>>>> +1 on revamp.
>>>> 
>>>> 
>>>> 
>>>> Sent from my Verizon Wireless 4G LTE smartphone
>>>> 
>>>> 
>>>> -------- Original message --------
>>>> From: Trevor Grant <trevor.d.gr...@gmail.com>
>>>> Date: 03/23/2017 12:36 PM (GMT-08:00)
>>>> To: user@mahout.apache.org, d...@mahout.apache.org
>>>> Subject: Marketing
>>>> 
>>>> Hey user and dev,
>>>> 
>>>> With 0.13.0 the Apache Mahout project has added some significant
>> updates.
>>>> 
>>>> The website is starting to feel 'dated' I think it could use a
> reboot.
>>>> 
>>>> The blue person riding the elephant has less signifigance in
>>>> Mahout-Samsara's modular backends.
>>>> 
>>>> Would like to open the floor to discussion on website reboot (and
>>>> who might be willing to take on such a project), as well as new
> mascot.
>>>> 
>>>> To kick off- in an offline talk there was the idea of A honey
>>>> badger (bc honey-badger don't care, just like mahout don't care
>>>> what back end or native solvers you are using, and also bc a cobra
>>>> bites a honey badger and he takes a little nap then wakes up and
>>>> finishes eating the cobra. honey badger eats snakes, and does all
>>>> the work while the other animals pick up the scraps.
>>>> see this short documentary on the honey badger:
>>>> https://www.youtube.com/watch?v=4r7wHMg5Yjg ) ^^audio not safe for
>>>> work
>>>> 
>>>> Con: its almost tooo jokey.
>>>> 
>>>> Other idea: are coy-wolfs.
>>>> 
>>>> 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*
>>>> 
>>>> 
>>> 
>>> ------------------------------------------------------------
>>> -----------------------
>>> This email message is for the sole use of the intended recipient(s)
>>> and may contain confidential information.  Any unauthorized review,
>>> use, disclosure or distribution is prohibited.  If you are not the
>>> intended recipient, please contact the sender by reply email and
>>> destroy all copies of the original message.
>>> ------------------------------------------------------------
>>> -----------------------
>>> 
>>> 
>> 
> 

Reply via email to