Ratio (Session) and Least Sessions
I wanted to fully understand the Ratio(Session) load balancing method.
I came across this question in the forums, but the links are old and it doesn't provide a clear answer, I want to know what exactly is considered a session in the Ratio(session), it's mentioned for the Least sessions that it depends on a Persistence profile (least number of entries in the persistence table) to determine the sessions for each pool member, for example HTTP cookie determines the session in this case, is it the same case for Ratio(Session)?
What is meant by a session exactly in the Ratio(Session) and is there a real-world example for this case?
In this article, it's mentioning that Ratio(Session) is used for protocols that transmit multiple messages over the same connection, is this the same case for HTTP for example using Cookie persistence like Least Sessions? It's not very clear to me how the system will count sessions if it's not based on persistence like the Least Sessions.
When I applied this load balancing method to a pool with multiple members, I noticed the requests where going to one member only.