POC: Global Cache #6100
Draft
POC: Global Cache #6100
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…, and create a sessionId hashing the global cache URL Signed-off-by: jorgee <[email protected]>
✅ Deploy Preview for nextflow-docs-staging canceled.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a test to validate the possibility of a global cache to share the task caching between executions. This is forcing to have the same cloud-cache, working dir and sessionId for a defined global-cache.It is able to detect when same task is executed by different workflows without using the resume option.
-with-globalcache=<cloud_path>parameter overwrites cloud cache path with<cloud_path>/.nf-global-cacheand the working dir with<cloud_path>/workand creates aSessionIdhashing the global cache path. This option implies-resume.I tested the concurrent execution of tasks in two different workflow and it is detecting if it is the same and generating a new hash. When executing a third workflow with the same task after the execution of the task it detects that is cached and do not run the task again.