airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Jayasekara (JIRA)" <>
Subject [jira] [Closed] (AIRAVATA-252) Remove invoker caching from Workflow interpreter
Date Tue, 17 Sep 2013 20:35:58 GMT


Amila Jayasekara closed AIRAVATA-252.

> Remove invoker caching from Workflow interpreter
> ------------------------------------------------
>                 Key: AIRAVATA-252
>                 URL:
>             Project: Airavata
>          Issue Type: Improvement
>            Reporter: Chathura Herath
>            Assignee: Saminda Wijeratne
>             Fix For: 0.9
> 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
For more information on JIRA, see:

View raw message