singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SINGA-36) Clean ModelProto, ClusterProto and JobProto
Date Thu, 23 Jul 2015 06:50:04 GMT


ASF subversion and git services commented on SINGA-36:

Commit c3a248a4b66e80e8c7c97778ea576bd09feaa412 in incubator-singa's branch refs/heads/master
from wang sheng
[;h=c3a248a ]

SINGA-36 Clean ModelProto, ClusterProto, JobProto and driver program

change singatool glog output
 * all logs will be directed to stderr
 * log level is LOG_ERROR

> Clean ModelProto, ClusterProto and JobProto
> -------------------------------------------
>                 Key: SINGA-36
>                 URL:
>             Project: Singa
>          Issue Type: Improvement
>            Reporter: wangwei
> Currently, we use the google protocol buffer to generate ClusterProto and ModelProto
classes for cluster (i.e., worker, server, group, etc) configuration and model (i.e., neuralnet,
updater, etc) configuration respectively. Theses classes provide functions to load/parse plain
text configuration files.
> To make the naming more representative and simplify the configuration process, this ticket
> * move worker, server and group configuration into JobProto, i.e., these configurations
are job/application specific.
> * move ModelProto as a field of JobProto, because the neuralnet configuration is also
job specific.
> * move zookeeper, hostfile, etc configuration into ClusterProto, because these fields
are shared by all jobs.
> The configuration for ClusterProto is done when installing SINGA and is done for only
once. The configuration file is fixed at $SINGA/conf/singa.conf.
> The configuration for JobProto is done every time a new job is submitted. The conf file
is $workspace/job.conf. Users submit the job by passing -conf=$workspace to ./bin/

This message was sent by Atlassian JIRA

View raw message