You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
Each input and output requires a WSM call to obtain the SAS token. However, the WSM API may fail to respond under stress conditions, such as when running large scatter-gather workflows.
Solution:
To reduce the frequency of WSM calls, by caching the SAS tokens while executing a node task.
AC:
Use container scoped JIT tokens in the runner to improve caching performance for both reading and writing operations.
Manage possible expiration scenarios, even though they are rare due to the JIT nature of the tokens.
Implementation in the URL transformation strategy for Terra.
The text was updated successfully, but these errors were encountered:
giventocode
changed the title
Optimize calls to WSM when executing task via the runner
Optimize calls to WSM when executing tasks via the runner
Oct 2, 2023
ngambani
changed the title
Optimize calls to WSM when executing tasks via the runner
[#148 Implement TES Task Runner] Optimize calls to WSM when executing tasks via the runner
Oct 4, 2023
Problem:
Each input and output requires a WSM call to obtain the SAS token. However, the WSM API may fail to respond under stress conditions, such as when running large scatter-gather workflows.
Solution:
To reduce the frequency of WSM calls, by caching the SAS tokens while executing a node task.
AC:
The text was updated successfully, but these errors were encountered: