perf(http/prom): avoid oneshot channel for request duration start time#4448
Merged
perf(http/prom): avoid oneshot channel for request duration start time#4448
Conversation
cratelyn
approved these changes
Mar 6, 2026
cratelyn
reviewed
Mar 6, 2026
cratelyn
reviewed
Mar 6, 2026
unleashed
force-pushed
the
amr/record-start-time-optimization
branch
from
af46927 to
9079c81
Compare
RecordRequestDuration knows the start time at call() time, whereas RecordResponseDuration defers it until the request body flushes. The latter needs async delivery from the request body wrapper, but the former is known synchronously. Replace the shared oneshot::Receiver<Instant> in ResponseState with an enum supporting both immediate and deferred start times, removing one heap allocation per request. Signed-off-by: Alejandro Martinez Ruiz <amr@buoyant.io>
unleashed
force-pushed
the
amr/record-start-time-optimization
branch
from
9079c81 to
e53c203
Compare
cratelyn
approved these changes
Mar 10, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
RecordRequestDuration knows the start time at call() time, whereas RecordResponseDuration defers it until the request body flushes. The latter needs async delivery from the request body wrapper, but the former is known synchronously.
Replace the shared oneshot::Receiver in ResponseState with an enum supporting both immediate and deferred start times, removing one heap allocation per request.