A request the S3 store took long to answer is logged as a warning #4

Merged
ferociousbyte merged 1 commit from main into stable 2026-11-19 19:19:22 +00:00

A store can take tens of seconds for a single request that then succeeds, and nothing said so: the client's request
was just slow. Measured against Hetzner's object storage (hel1, 500 rounds of a 700 KB write and two reads of 8 KB,
from one machine, 2026-11-19): about 1 request in 100 took more than 10 s and the longest 55 s, each one HTTP
request without a retry or a new connection, answered correctly in the end. In a region the completion of an upload
waited 48 s for the first 8 KB of the file it had just written.

From s3:slowRequestMilliseconds on (2000; 0 for none) the store now logs what it asked, for which key and how long
the answer took, also when the request failed. That is the time to the answer's headers, with whatever the SDK
tried again. A write whose content comes as a stream is not timed: it is as slow as whoever sends it.

Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com

A store can take tens of seconds for a single request that then succeeds, and nothing said so: the client's request was just slow. Measured against Hetzner's object storage (hel1, 500 rounds of a 700 KB write and two reads of 8 KB, from one machine, 2026-11-19): about 1 request in 100 took more than 10 s and the longest 55 s, each one HTTP request without a retry or a new connection, answered correctly in the end. In a region the completion of an upload waited 48 s for the first 8 KB of the file it had just written. From s3:slowRequestMilliseconds on (2000; 0 for none) the store now logs what it asked, for which key and how long the answer took, also when the request failed. That is the time to the answer's headers, with whatever the SDK tried again. A write whose content comes as a stream is not timed: it is as slow as whoever sends it. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A request the S3 store took long to answer is logged as a warning
All checks were successful
/ build (push) Successful in 1m3s
/ push (push) Successful in 35s
c7e4076807
A store can take tens of seconds for a single request that then succeeds, and nothing said so: the client's request
was just slow. Measured against Hetzner's object storage (hel1, 500 rounds of a 700 KB write and two reads of 8 KB,
from one machine, 2026-11-19): about 1 request in 100 took more than 10 s and the longest 55 s, each one HTTP
request without a retry or a new connection, answered correctly in the end. In a region the completion of an upload
waited 48 s for the first 8 KB of the file it had just written.

From s3:slowRequestMilliseconds on (2000; 0 for none) the store now logs what it asked, for which key and how long
the answer took, also when the request failed. That is the time to the answer's headers, with whatever the SDK
tried again. A write whose content comes as a stream is not timed: it is as slow as whoever sends it.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
unilayer/storage!4
No description provided.