-
Notifications
You must be signed in to change notification settings - Fork 134
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
feat(quic): quic fine tune #267
Conversation
@@ -691,8 +694,8 @@ connect(Parent, N, PubSub, Opts) -> | |||
undefined when TopicPayloadRend == undefined -> | |||
erlang:send_after(RandomPubWaitMS, self(), publish); | |||
undefined -> | |||
maps:foreach(fun(TopicName, #{name := TopicName}) -> | |||
erlang:send_after(RandomPubWaitMS, self(), {publish, TopicName}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the use of the random wait was intentional: to stagger publishing over a wider period of time instead of a huge simultaneous burst.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is for topic payload --topics-payload
option, we don't want publisher send pkts immediately(regardless of random wait) after connect.
maybe change it to
RandomPubWaitMS + DelayMs
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, that sounds good
deb45ad
to
d5ab65d
Compare
Also fixed a dumb bug relates to |
This is breaking change:
old
--quic
now must come with--quic true
as arg type changes.new
--quic fine_tune.eterm
is supported for fine tune the quic conn and quic ctrl stream.