-
Notifications
You must be signed in to change notification settings - Fork 37
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
Channel max part2 #945
Channel max part2 #945
Conversation
It's probably insane to open more than (or even close to) |
Well, that is not possible. There is a limit to how many electrons there are in the universe. Or maybe not. But a limit to how many we have access to :) |
e33967a
to
40b626d
Compare
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.
With channel_max = 0
in config:
# lavinmqperf connection-count -x 1 -c 100000 --uri 'amqp://guest:guest@localhost/%2F?channel_max=0'
Unhandled exception in spawn: channel_max reached (Exception)
Do we want channel ids to be |
Actually 0 is not "unlimited" it's
And channel ids are |
I was confused by the commit message |
Oh, didn't update before i wrote my last comment! 👍 |
WHAT is this pull request doing?
Was i little trigger happy with the prio PR....
Question: How do we handle the "hard" limit of
UInt16::MAX
?Should we communicate that? Or have it as a "hidden" limit?
HOW can this pull request be tested?
Specs