reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yunseong Lee (JIRA)" <>
Subject [jira] [Commented] (REEF-1000) Allow more configuration in VortexLauncher
Date Wed, 09 Dec 2015 16:10:12 GMT


Yunseong Lee commented on REEF-1000:

I made a PR for this

One thing slightly different from the comments above, is {{getVortexConf}}. Since it is useful
to set a configuration with minimal required parameters, I left as it is. Instead, users might
use {{VortexMasterConf}} to bind additional variables (e.g., {{CallbackThreadpoolSize}}) if
they want.

> Allow more configuration in VortexLauncher
> ------------------------------------------
>                 Key: REEF-1000
>                 URL:
>             Project: REEF
>          Issue Type: Improvement
>          Components: Vortex
>            Reporter: Yunseong Lee
>            Assignee: Yunseong Lee
> Vortex launcher takes fixed type of configuration variables, and most of them are related
to resource configuration: numWorkers, workerMemory, workerCores, workerCapacity. In our HelloVortex
example, the launcher code looks like following.
> {}
> VortexLauncher.launchLocal("Vortex_Example_HelloVortex", HelloVortexStart.class, 1, 1024,
1, 2000);
> {code}
> The launcher code looks very simple, and user can easily figure out which parameters
are needed from IDE. But this is quite rigid.
> # When user wants to change the configuration, she/he should rebuild the project.
> # There would be more parameters than the current configuration. We already have REEF-517,
but that issue is not about the way we set values.
> # Users may want to set configuration specific to application. For example, in {{AddOne}}
example, we may want to set the dimension of Vector at runtime.
> It would be great for users to do this without much effort. Using Tang would be awesome
because they provide {{CommandLine}}.

This message was sent by Atlassian JIRA

View raw message