Skip to content
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

dvc cache dir: carry over the existing cache #3300

Closed
dmpetrov opened this issue Feb 10, 2020 · 1 comment
Closed

dvc cache dir: carry over the existing cache #3300

dmpetrov opened this issue Feb 10, 2020 · 1 comment
Labels
awaiting response we are waiting for your reply, please respond! :) question I have a question?

Comments

@dmpetrov
Copy link
Member

What do I suppose to do with the existing cache dir after dvc cache dir ../../my_shared_cache? Probably I should copy it to the new one (cp -r .dvc/cache/* ../../my_shared_cache && rm -rf .dvc/cache ).

Is there any reason why the command does not do that by default (or through some option like --carry-over)?

@dmpetrov dmpetrov added the question I have a question? label Feb 10, 2020
@efiop
Copy link
Contributor

efiop commented Feb 12, 2020

@dmpetrov cp & rm will be really slow, but I do understand that you've suggest it because it would be atomic unlike moving files one by one. The main reason we don't do it is because it is very heavy-weight and often the cache dir we move to already has something in it (e.g. shared machine scenario). Doing that by default would be a bit too much. Though, maybe dvc cache move would be a solution? Not sure if we should take on that functionality in dvc itself, feels like it is out of our focus.

@efiop efiop added the awaiting response we are waiting for your reply, please respond! :) label Feb 15, 2020
@efiop efiop closed this as completed Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting response we are waiting for your reply, please respond! :) question I have a question?
Projects
None yet
Development

No branches or pull requests

2 participants