reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joo Seong (Jason) Jeong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1520) Enable concurrent processing of .NET driver-side events
Date Thu, 11 Aug 2016 06:27:20 GMT

    [ https://issues.apache.org/jira/browse/REEF-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416635#comment-15416635
] 

Joo Seong (Jason) Jeong commented on REEF-1520:
-----------------------------------------------

We may not have to address this issue, depending on how [REEF-334|https://issues.apache.org/jira/browse/REEF-334]
is resolved.

> Enable concurrent processing of .NET driver-side events
> -------------------------------------------------------
>
>                 Key: REEF-1520
>                 URL: https://issues.apache.org/jira/browse/REEF-1520
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF Driver, REEF.NET Driver
>    Affects Versions: 0.16
>            Reporter: Joo Seong (Jason) Jeong
>
> A .NET driver is backed by a Java driver, with driver-side events being delegated from
Java to .NET via JNI. However, for the ease of development, we currently have setup all events
to be processed one at a time, sequentially.
> {code:Java}
> // org.apache.reef.javabridge.generic.JobDriver
> public void onNext(final AllocatedEvaluator allocatedEvaluator) {
>   synchronized (JobDriver.this) {
>     ..
>   }
> }
> public void onNext(final ActiveContext context) {
>   synchronized (JobDriver.this) {
>     ..
>   }
> }
> {code}
> Concurrent processing is NOT inherently impossible, since we already have it on the Java
side. We can make improvements to the code so that concurrency is allowed for the .NET side
too.



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

Mime
View raw message