You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/05/17 21:12:13 UTC

[jira] [Commented] (NIFI-1822) Allow concurrent execution of ExecuteScript

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

ASF GitHub Bot commented on NIFI-1822:
--------------------------------------

Github user pvillard31 commented on the pull request:

    https://github.com/apache/nifi/pull/443#issuecomment-219855457
  
    Maven build with contrib-check OK.
    Reviewed and it LGTM, nice unit testing.
    Tested with two different flows and it is working as expected.
    I'm a +1


> Allow concurrent execution of ExecuteScript
> -------------------------------------------
>
>                 Key: NIFI-1822
>                 URL: https://issues.apache.org/jira/browse/NIFI-1822
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>             Fix For: 1.0.0, 0.7.0
>
>
> Currently ExecuteScript is annotated as TriggerSerially, meaning only one task can be running at a time. This causes issues for throughput, and can become a severe bottleneck in a flow.
> Originally this was done because the bindings for the session, context, etc. were put on a single script engine, so multiple tasks would clobber each other's bindings. However as a tradeoff (memory for capability), it would be better to have a "pool" of Script Engine instances, whose size is perhaps the max number of concurrent tasks.



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