mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #1543] Run integration tests with larger files #811
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#811
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gaul on GitHub (Feb 2, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1543
s3fs sets
BIG_FILE_LENGTHto 25 MB which is large enough to trigger multipart upload but lower than other limits like the single file upload size. This limit also makes sense when using S3Proxy's transient backend which store objects in-memory. When apache/jclouds#96 merges, s3fs can instead use the filesystem backend which stores objects on-disk. This will allow the integration tests to use larger objects, e.g., > 5 GB single-part objects. Related to #1542.@gaul commented on GitHub (Feb 4, 2021):
With larger files reading from
/dev/urandombecomes a bottleneck. We may want to create our own helper which makes pseudo-random data faster.@gaul commented on GitHub (Feb 4, 2021):
To use the filesystem blobstore to test larger files we will need a new release of S3Proxy to include the jclouds fix.
@gaul commented on GitHub (Feb 7, 2021):
Testing with larger files is proving to be a rich source of bugs. Some tests require files as large as 11 GB to trigger various conditions which takes up to 15 minutes to run on my desktop. We could add some flags to s3fs and S3Proxy to use smaller thresholds to trigger conditions like copy part range more easily.
@gaul commented on GitHub (May 30, 2021):
Related to #1665, currently blocked on macOS Java xattr compatibility.