You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Chathura Herath (Created) (JIRA)" <ji...@apache.org> on 2011/12/27 19:10:30 UTC
[jira] [Created] (AIRAVATA-252) Remove invoker caching from
Workflow interpreter
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
Fix For: 0.3-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
[jira] [Assigned] (AIRAVATA-252) Remove invoker caching from
Workflow interpreter
Posted by "Chathura Herath (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chathura Herath reassigned AIRAVATA-252:
----------------------------------------
Assignee: Saminda Wijeratne
> 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.3-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
[jira] [Updated] (AIRAVATA-252) Remove invoker caching from
Workflow interpreter
Posted by "Suresh Marru (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Marru updated AIRAVATA-252:
----------------------------------
Fix Version/s: (was: 0.4-INCUBATING)
0.5-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.5-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
[jira] [Updated] (AIRAVATA-252) Remove invoker caching from
Workflow interpreter
Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lahiru Gunathilake updated AIRAVATA-252:
----------------------------------------
Moving this jira to 0.5 release since this is not critical for 0.4.
Lahiru
> 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
[jira] [Updated] (AIRAVATA-252) Remove invoker caching from
Workflow interpreter
Posted by "Lahiru Gunathilake (Updated) (JIRA)" <ji...@apache.org>.
[ 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