Is this performance penalty only observed because of new connections being done
at a high rate, or even after the large number of connections is established?
The limit should be enforced only when accepting new connection, if it does in
other cases, it is then some mistake.
Disabling this limit checking is indeed good to have, I pushed a commit so in
case the parameter is set to 0 or negative value, the limiting is no longer
done (e3e6fd75bdd688acebf0ec8a1b7efa6fcada1de6). The commit can be backported
if you have the chance to test it and works as expected.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3759#issuecomment-1954702980
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3759/1954702...@github.com>
_______________________________________________
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
