mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Schelter (JIRA)" <>
Subject [jira] [Commented] (MAHOUT-1529) Finalize abstraction of distributed logical plans from backend operations
Date Fri, 02 May 2014 06:59:15 GMT


Sebastian Schelter commented on MAHOUT-1529:

The problem with having a no-arg materialize operator is that our optimizer would have to
make the decision how to materialize the data for spark (in-memory, in-memory in a serialized
fashion, on disk). I don't think that we can/should make that decision ourselves. If people
run into OOMs with spark we have to give them something to work around that (e.g. allow them
to tell the system to use a different storage level).

What do you think about keeping those storagelevels, but interpret them as hints to the underlying
system, which indicates to the user that the system might make a (hopefully) smarter decision,
e.g. something like


> Finalize abstraction of distributed logical plans from backend operations
> -------------------------------------------------------------------------
>                 Key: MAHOUT-1529
>                 URL:
>             Project: Mahout
>          Issue Type: Improvement
>            Reporter: Dmitriy Lyubimov
>             Fix For: 1.0
> We have a few situations when algorithm-facing API has Spark dependencies creeping in.

> In particular, we know of the following cases:
> (1) checkpoint() accepts Spark constant StorageLevel directly;
> (2) certain things in CheckpointedDRM;
> (3) drmParallelize etc. routines in the "drm" and "sparkbindings" package. 
> (5) drmBroadcast returns a Spark-specific Broadcast object

This message was sent by Atlassian JIRA

View raw message