mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-24 21:06:02 +03:00
[PR #859] [MERGED] Upload S3 parts without batching #1665
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#1665
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?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/859
Author: @gaul
Created: 11/16/2018
Status: ✅ Merged
Merged: 11/18/2018
Merged by: @ggtakec
Base:
master← Head:upload-remove-batching📝 Commits (1)
88cd8feUpload S3 parts without batching📊 Changes
3 files changed (+150 additions, -45 deletions)
View changed files
📝
src/curl.cpp(+82 -45)📝
src/curl.h(+3 -0)➕
src/psemaphore.h(+65 -0)📄 Description
Previously s3fs would issue a batch of uploads and wait for all to
succeed before issuing the next batch. Now it issues the first batch
and only waits for a single part to succeed before uploading the next
part. This can improve performance when one part lags due to network
errors. Fixes #183.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.