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

Switch deployment on drogon to use dandidav + davfs2 instead of datalad-fuse #76

Closed
yarikoptic opened this issue Jun 10, 2024 · 2 comments · Fixed by #77
Closed

Switch deployment on drogon to use dandidav + davfs2 instead of datalad-fuse #76

yarikoptic opened this issue Jun 10, 2024 · 2 comments · Fixed by #77
Assignees
Labels
asset access How the program gets the assets and lists thereof datalad-fuse Relating to accessing assets over a datalad-fuse mount performance More efficient use of time and space WebDAV Relating to accessing assets over a WebDAV mount

Comments

@yarikoptic
Copy link
Member

Follow up to results from

@jwodder
Copy link
Member

jwodder commented Jun 12, 2024

@yarikoptic Should any of the code for working with datalad-fuse and/or benchmarking different mount types be kept after this?

@yarikoptic
Copy link
Member Author

Let's keep for now... may be we would make datalad-fuse speedy or decide to benchmark more of setups

jwodder added a commit that referenced this issue Jun 12, 2024
Replace datalad-fuse with davfs2
@jwodder jwodder added datalad-fuse Relating to accessing assets over a datalad-fuse mount WebDAV Relating to accessing assets over a WebDAV mount performance More efficient use of time and space asset access How the program gets the assets and lists thereof labels Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
asset access How the program gets the assets and lists thereof datalad-fuse Relating to accessing assets over a datalad-fuse mount performance More efficient use of time and space WebDAV Relating to accessing assets over a WebDAV mount
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants