[
https://issues.apache.org/jira/browse/AIRAVATA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Gunathilake updated AIRAVATA-252:
----------------------------------------
Fix Version/s: (was: 0.3-INCUBATING)
0.4-INCUBATING
> Remove invoker caching from Workflow interpreter
> ------------------------------------------------
>
> Key: AIRAVATA-252
> URL: https://issues.apache.org/jira/browse/AIRAVATA-252
> Project: Airavata
> Issue Type: Improvement
> Reporter: Chathura Herath
> Assignee: Saminda Wijeratne
> Fix For: 0.4-INCUBATING
>
>
> Currently in XBaya workflow interpreter we cache the invokers. THis was done
> so that if the user reruns the workflow we could reuse the invoker as well as
> we could simply use it as the service output store.
> Two issues with this are;
> 1)If the invoker is cached and at a later time reused if the time between
> reuse is more than proxy expire time, it will fail and reuse cannot be made
> anyway
> 2) Statistically cases that will reuse the invoker is much less than cases
> that it will use once. So this performance gain can be let go of a memory
> gain. If the user is rerunning, user is in the execution cycle and
> performance gain will anyway go unnoticed
> So i propose to remove the invoker map and store the output in the workflow
> node itself in the graph as possible Futures object.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
