[jira] [Created] (AIRAVATA-1620) Optimize thread usage in Workflow Enactment Service.

["Shameera Rathnayaka (JIRA)" <ji...@apache.org>]

Shameera Rathnayaka created AIRAVATA-1620:
---------------------------------------------

             Summary: Optimize thread usage in Workflow Enactment Service.
                 Key: AIRAVATA-1620
                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1620
             Project: Airavata
          Issue Type: Improvement
            Reporter: Shameera Rathnayaka
            Assignee: Shameera Rathnayaka


Currently new workflow model allocates a thread from the thread pool to run the workflow and thread comes back to the thread pool after finishing the all workflow nodes executed in that workflow. As the nature of the workflows runs on real case, this workflows may take days to complete. In this case, it is not idea to allocate a thread until it finishes, most of the time thread is in sleep state and only need to run once the task events trigger for the submitted task.

We can optimize the thread utilization by allowing thread to come back to the thread pool till the next task output  and status event trigger. Workflow enactment service keep listening to the all task events and invoke correct workflow and hand over the event. 



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