Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
nghttpx: Use an existing h2 backend connection as much as possible
h2load measurement reveals that this strategy is 3 times faster than the previous implementations.
- Loading branch information
1 parent
aaa0b85
commit f507b5e
Showing
1 changed file
with
30 additions
and
46 deletions.
There are no files selected for viewing
This file contains 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
f507b5e
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.
Hello,
first of all, I did not find any support forums, so please feel free to redirect me somewhere else if commenting here is in any way inappropriate.
I tracked down this commit while searching for a reason why my loadbalancer is not loadbalancing :)
I have a setup with 2 gRPC backends in the same lb group and I want to balance incoming traffic between these two (all the traffic is coming to the frontend from the same IP). Before this (<1.27.0), everything is working as I would expect. This commit causes nghttpx to consistently reuse the connection to first backend and it never even attempts to connect to the second backend. Is this the desired behaviour? Please, correct me if I am doing something wrong (and I may be as this is my first contact with nghttpx), but in my opinion, this is not loadbalancing :)
Regards,
Tom
f507b5e
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.
Oh, I just noticed this was reverted in master 9 hours ago :) Nevermind.
Have a nice day,
Tom