singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "wangwei (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SINGA-57) Improve Distributed Hogwild
Date Sat, 26 Sep 2015 15:13:04 GMT

     [ https://issues.apache.org/jira/browse/SINGA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

wangwei resolved SINGA-57.
--------------------------
    Resolution: Fixed

> Improve Distributed Hogwild
> ---------------------------
>
>                 Key: SINGA-57
>                 URL: https://issues.apache.org/jira/browse/SINGA-57
>             Project: Singa
>          Issue Type: Improvement
>            Reporter: wangwei
>
> The implementation SINGA-8 of distributed Hogwild uses the stub thread to monitor the
network bandwidth. When the network has >0 bandwidth, the stub sends a sync reminder msg
to a server, which would trigger the server to sync one param slice with other server groups.
> The code is messy due to the monitoring of network bandwidth and processing the sync
reminder message. Another problem is that the  reminder message may not be generated frequently.
Because it is generated only when the router times out. If the worker and server run very
fast that the router rarely times out, then the sync reminder message cannot be sent. In contrast,
if the router times out frequently, many reminder messages would be generated.
> This ticket improves the implementation by fixing the frequency of synchronization between
server groups. A server sends a sync message for a Param (slice) for every sync_freq updates
to the server group that masters/maintains the Param.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message