Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

queue up to 32 DATAGRAM frames to send #4222

Merged
merged 1 commit into from
Jan 1, 2024
Merged

Conversation

marten-seemann
Copy link
Member

@marten-seemann marten-seemann commented Dec 29, 2023

Fixes #3766.

@birneee Could you give this PR a try? Does it improve the datagram performance for your use case?

@marten-seemann marten-seemann added this to the v0.41 milestone Dec 29, 2023
Copy link

codecov bot commented Dec 29, 2023

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (7f080dd) 83.96% compared to head (93d8263) 83.99%.

Files Patch % Lines
datagram_queue.go 91.67% 2 Missing and 1 partial ⚠️
connection.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4222      +/-   ##
==========================================
+ Coverage   83.96%   83.99%   +0.04%     
==========================================
  Files         149      149              
  Lines       15410    15419       +9     
==========================================
+ Hits        12938    12951      +13     
+ Misses       1973     1970       -3     
+ Partials      499      498       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

"github.com/quic-go/quic-go/internal/utils"
"github.com/quic-go/quic-go/internal/wire"
)

const (
maxDatagramSendQueueLen = 32
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make this configurable to let the users experiment with different queue size?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really want to add additional API surface here, but if your experimentation finds that this queue is too small, we can increase the queue size.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

magic environment variables would be useful here. Can label it alpha or beta to let people know it's going away

@marten-seemann marten-seemann changed the base branch from discard-too-large-datagrams to master January 1, 2024 03:18
@marten-seemann marten-seemann merged commit 1fce81f into master Jan 1, 2024
18 checks passed
@marten-seemann marten-seemann deleted the datagram-queue-length branch January 1, 2024 04:00
nanokatze pushed a commit to nanokatze/quic-go that referenced this pull request Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Poor datagram extension send performance
3 participants