On Mar 2, 2015, at 8:34 AM, RESTOUX, Loïc <loic.restoux@capgemini.com> wrote:
The weird thing is that if we move the use of rlm_rest in another section like pre-proxy, there is no blocking issue any more.
Except the rest module doesn’t have a pre-proxy or post-proxy method. So… what exactly are you doing?
We used radperf for benchmark (-p 500). The results: - No REST request at all => freeradius handles 3800 requests per sec approximately. - if the REST server is called in pre-proxy => 1100 r/s. All the threads of the pool are active. - if the REST server is called in post-proxy => between 70and 150 r/s with a lot of variation between our tests. Less than half of available threads are active.
Is the behaviour the same if you change rest for another module? Alan DeKok.