You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Yingda Chen (JIRA)" <ji...@apache.org> on 2015/05/06 18:51:01 UTC
[jira] [Commented] (REEF-310) Memory utilization for class
hierarchies is O(#contexts) in the bridge
[ https://issues.apache.org/jira/browse/REEF-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14530884#comment-14530884 ]
Yingda Chen commented on REEF-310:
----------------------------------
Is this JIRA suggesting that we want to enforce class hierarchy to be a single instance in one job submission? Not sure if that is a good idea, it seem reasonable to want different class hierarchy in different contexts, say a graph context and a streaming context (even though we do not have full support for that at the moment).
> Memory utilization for class hierarchies is O(#contexts) in the bridge
> ----------------------------------------------------------------------
>
> Key: REEF-310
> URL: https://issues.apache.org/jira/browse/REEF-310
> Project: REEF
> Issue Type: Improvement
> Components: REEF Bridge
> Reporter: Markus Weimer
> Priority: Minor
> Labels: Performance
>
> In {{ActiveContextBridge}}, we load the class hierarchy for the C# side in the constructor (thanks to [REEF-304]). However, we load the *same* class hierarchy for all contexts. Also, we don't seem to modify it. This creates a memory complexity of O(#contexts), where it really could be O(1).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)