Update S3 recommendations to use s3fs #72
Merged
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
pieper
reviewed
Jul 3, 2025
Co-authored-by: Steve Pieper <[email protected]>
Contributor
Author
|
We might want to coordinate updating this with whatever we do about ImagingDataCommons/idc-index#168 |
fedorov
approved these changes
Jul 9, 2025
fedorov
added a commit
to ImagingDataCommons/IDC-Tutorials
that referenced
this pull request
Jul 9, 2025
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.
I found
s3fsand it is much faster thansmart_openfor this use case (I think due to better caching behavior). Updating the recommendations to recommend it instead