docs(blog): clarify HTTP/3 proxy rationale in one-core bottleneck article#207
Merged
Merged
Conversation
…icle - Add summary Callout near top clarifying that disabling HTTP/3 was not the fix - Add protocol boundary note (client->proxy HTTP/3, proxy->backend HTTP) - Enhance Phase 2 conclusion to explicitly state QUIC was not the driver - Add HTTP/3 as a separate product/ops decision in Final Operational Decision - Add follow-up references for torrust-tracker-demo#31 and torrust-tracker#1736 Closes #198
There was a problem hiding this comment.
Pull request overview
This PR updates the “one-core softirq bottleneck” blog article to clearly separate the Phase 2 HTTP/3 (QUIC) disablement experiment from the actual remediation (enabling RPS/RFS), and adds protocol-boundary clarification plus follow-up issue links for traceability.
Changes:
- Add an early warning callout explicitly stating HTTP/3 disablement was not the root-cause fix, and that RPS/RFS packet steering was.
- Strengthen the Phase 2 conclusion to state QUIC on UDP 443 was not driving the hotspot, and frame HTTP/3 as an ops/product decision.
- Add follow-up issue references (torrust-tracker-demo#31, torrust-tracker#1736) in the operational decision and references sections.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Member
Author
|
ACK 99c0d15 |
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.
Summary
Clarify that disabling HTTP/3 was not the root-cause fix for the one-core softirq bottleneck, and that RPS/RFS packet steering was the actual remediation. Also add protocol boundary notes and link follow-up issues for traceability.
Changes
Related issue
Closes #198
Checklist
npm run lintpassesnpm run checkpasses