Log when active streams reaches and drops below max concurrent streams #974
Conversation
This file contains 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
Lukasa
reviewed
Sep 25, 2020
Sources/GRPC/GRPCIdleHandler.swift
Outdated
| }, uniquingKeysWith: { a, _ in a }) | ||
| ) | ||
|
|
||
| let maxConcurrentStreams = settings.first(where: { $0.parameter == .maxConcurrentStreams }) |
There was a problem hiding this comment.
A quick FYI: if there are multiple instances of a setting in a HTTP/2 settings frame, the last instance of the setting is the one that counts. HTTP2Settings is a RandomAccessCollection so you can do reversed() for free.
There was a problem hiding this comment.
Oh, good catch. Thanks!
Motivation: Reaching max concurrent streams will cause frames on additional streams to be buffered, and can therefore see increased latency. Observing this is difficult. Modifications: - Log any changes in HTTP/2 settings, not just the initial settings - Add a warning log when our active stream count matches max concurrent streams - Add a notice log when our stream count drops below max concurrent streams Result: Better observability when we get close to max concurrent streams.
glbrntt
force-pushed
the
gb-warn-on-max-streams-limit
branch
from
9eb424d to
ac1116c
Compare
Lukasa
approved these changes
Sep 25, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation:
Reaching max concurrent streams will cause frames on additional streams
to be buffered, and can therefore see increased latency. Observing this
is difficult.
Modifications:
streams
streams
Result:
Better observability when we get close to max concurrent streams.