mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[PR #914] [MERGED] Issue readdir HEAD requests without batching #1697
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#1697
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/914
Author: @gaul
Created: 1/21/2019
Status: ✅ Merged
Merged: 1/21/2019
Merged by: @ggtakec
Base:
master← Head:readdir/head-of-line📝 Commits (1)
46d79c5Issue readdir HEAD requests without batching📊 Changes
4 files changed (+92 additions, -98 deletions)
View changed files
📝
src/curl.cpp(+17 -31)📝
src/curl.h(+8 -4)📝
src/psemaphore.h(+13 -3)📝
src/s3fs.cpp(+54 -60)📄 Description
Previously s3fs would issue a batch of HEAD requests and wait for all
to succeed before issuing the next batch. Now it issues the first
batch and only waits for a single call to succeed before issuing the
next call. This can improve performance when one call lags due to
network errors. I measured 25% improvement with the same level of
parallelism. This commit also reparents parallelism knobs for
consistency. Follows on to
88cd8feb05.Fixes #223.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.