Hi all,
In our setup, we are doing ssl termination at HAProxy. Session stickyness
is also needed based on JSESSIONID cookie.
Currently, we achieved this by using appsession JESSIONID and we use
currently HAProxy 1.5.
With high volume of data/users, the CPU of that single core goes to 100%.
I understand that more than 1 HAProxy process can be configured (nbproc)
and via cpu-map and bind-process you can specify to which cores these
processes might bind.
I also understand that the table with cookies is kept in memory and memory
cannot be shared between the different processes.
Is there a way how can we scale this to more cores while still having
session stickyness?
Thanks in advance,
Peter
In our setup, we are doing ssl termination at HAProxy. Session stickyness
is also needed based on JSESSIONID cookie.
Currently, we achieved this by using appsession JESSIONID and we use
currently HAProxy 1.5.
With high volume of data/users, the CPU of that single core goes to 100%.
I understand that more than 1 HAProxy process can be configured (nbproc)
and via cpu-map and bind-process you can specify to which cores these
processes might bind.
I also understand that the table with cookies is kept in memory and memory
cannot be shared between the different processes.
Is there a way how can we scale this to more cores while still having
session stickyness?
Thanks in advance,
Peter