Ruslan Kuprieiev
Ruslan Kuprieiev
When working with local repos, dvc uses a lot of `exists()` and `stat()` calls, which is fine with normal filesystems, but could be extremely slow with filesystems like nfs/cifs/etc (e.g....
E.g. `dvc get https://github.com/user/proj /path/to/data` -> `dvc get https://github.com/user/proj path/to/data`. https://discordapp.com/channels/485586884165107732/485596304961962003/633731542539173889 So far, not seeing any reason against it.
As @shcheklein suggested, we should consider splitting data into small blocks to track data changes more efficiently. Example: giant file that has one line appended to it.
~~UPDATE: Possibly as a How To guide (see #899)~~ Looks like we need a special section describing ways how to organize your projects: - [ ] how to use DVC...
I.e. mount it to some dir and specify it as a local dir repository for dvc.
### Which service(blob, file, queue, table) does this issue concern? blob ### Which version of the Azurite was used? 3.10.0 ### Where do you get Azurite? (npm, DockerHub, NuGet, Visual...
Checklist - [x] Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml". - [x] License file is packaged (see [here](https://github.com/conda-forge/staged-recipes/blob/5eddbd7fc9d1502169089da06c3688d9759be978/recipes/example/meta.yaml#L64-L73) for an example). - [x] Source is...
We have get/import/ls for dvc repos, but only get-url and import-url for clouds. With cloud workflows in mind, we need `dvc ls-url` to be able to list files on clouds...