-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how-to: setup a shared cache (extracted from use cases) #2482
Conversation
and extract guided info to new how-to
This comment has been minimized.
This comment has been minimized.
draft a first section on storage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good iteration of the use case - close to what we've been doing with other use cases. A bit of polishing is still required, but it's a good one indeed! We are close.
@shcheklein I've repurposed this to only move the shared cache info to the guide for now. The existing use case will remain untouched but no longer linked from everywhere. Please review content/docs/user-guide/how-to/share-a-dvc-cache.md when you have a chance. All other changes are links and sidebar. |
content/docs/command-reference/gc.md
Outdated
specify a list of them (each project is a path) to keep data that is currently | ||
referenced from them. | ||
shared among different projects (e.g. as described | ||
[here](/doc/use-cases/sharing-resources-efficiently)), this option can be used |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's not part of this PR, right? should the use case one go first?
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
should the use case one go first?
Hmm the order isn't that important I think. Since this one is ready, why not go for it. This way we don't need to worry about where to put the shared cache info. later when the shared dev server use case changes completely.
content/docs/use-cases/versioning-data-and-model-files/index.md
Outdated
Show resolved
Hide resolved
|
||
# How to Share a DVC Cache | ||
|
||
There are 2 main reasons to setup a shared <abbr>DVC cache</abbr>: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
both items are pretty hard to read to be honest
so, we have a few cases people would use this:
- one large machine (e.g. with multiple GPUs) and one storage on it and people do the same or multiple projects and we want to avoid duplication (no copies) and save time (no copy)
- one large NAS () and people attach it to their machines - again no copies - fast, doesn't take extra space, fits even if there are no space (ability to work with really large data)
what else am I missing? can we make description more explicit/simpler?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. Updated, PTAL.
0611d2a
to
a350e4d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are two images - do we use those?
Do we need to setup a redirect?
per static/img/resource-pool.png
🤦 removed the images. No doc is removed yet so I see no need for a redirect here. I did change all the relevant links to the how-to for now. #2587 will have the redirect though. |
REPURPOSED to close #2487
Would close (no longer) #654 (comment)
And (not yet) #820