Hello,
I’m experimenting with nginx module development by trying to implement a random
load balancer.
I see that *us->servers->nelts matches the upstream servers defined in
nginx.conf
However, something that’s confusing to me is where *us->elts[0]->naddrs comes
from.
My thinking was that I c
Hi,
> Certainly things will be different if
> requests are not equal, though this is what least_conn is expected
> to address (and again, it does so better than just testing two
> choices).
Awesome, I hope to address this issue in my research. My suspicion is
that round-robin and random will c
> On the other hand, there is API in nginx which allows to implement
> any load balancing algorithm needed.
Cool! I was looking for something like that.
> As for the algorithms you've mentioned, "power of two choices" seems
> to be better than random, though it does not look like it is
> benef
Hello,
I’m Adam and I’ve been researching load balancing for my undergraduate senior
project. I’m particularly interested in the behavior of the “power of two
choices” and join-idle-queue algorithms on Nginx.
I’ve found that the `ngx_http_upstream_module` specifies a `least_conn` and
`least_ti