[WIP] Update Ktor with 3.6.0 - #1204
Draft
bjhham wants to merge 2 commits into
Draft
Conversation
Contributor
|
👋 Heads up! This PR modifies the following frameworks:
|
Contributor
Author
|
/benchmark -f ktor |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
Contributor
Author
|
/benchmark -f ktor |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
Contributor
Author
|
The h3 bottleneck looks better now except for static files going down to 37 rps lol. I'll investigate this one next. |
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
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.
Description
In 3.6.0, we're introducing HTTP/3 support and improving memory allocations in a few places. In anticipation of the release, I thought I'd run an early access build against the HttpArena benchmarks to see how it performs. I'll update this PR with the proper release artifact after it is published.
Fixes