You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@systemml.apache.org by "Matthias Boehm (JIRA)" <ji...@apache.org> on 2017/11/30 22:15:00 UTC

[jira] [Closed] (SYSTEMML-1984) Robustness JMLC wrt non-thread-local prepare and execute

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

Matthias Boehm closed SYSTEMML-1984.
------------------------------------
       Resolution: Fixed
         Assignee: Matthias Boehm
    Fix Version/s: SystemML 1.0

> Robustness JMLC wrt non-thread-local prepare and execute
> --------------------------------------------------------
>
>                 Key: SYSTEMML-1984
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-1984
>             Project: SystemML
>          Issue Type: Task
>            Reporter: Matthias Boehm
>            Assignee: Matthias Boehm
>            Priority: Blocker
>             Fix For: SystemML 1.0
>
>
> The JMLC API has an underlying assumption that prepared scripts are created and executed by the same thread because compiler configurations and output variable names for dynamic recompilation are maintained with thread-local variables. However, in complex scoring pipelines this is not the case leading to performance issues (e.g., multi-threaded operations despite single-threaded configuration) and in the worst case lost result variables. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)