Alan and other list member, It seems that the difference of performance is due to multi thread feature. When running freeradius with -s option ( single mode ) I have similar performance than in debug mode. That make sense as -X is equivalent to -sfxx -l stdout.
So new questions are: How can I take benefits of freeradius multi thread option and keeping good response time ? According to the man page "Some systems have issues with threading" is there any system configuration that can help ? And finally if I decide to stick to single mode how can I modify the /et/init.d/freeradius to use the -s option ? Many thanks in advance for your support. Vincent On Mon, Sep 7, 2009 at 10:30 PM, Alan DeKok<[email protected]> wrote: > Vincent Laborie wrote: >> Many thanks for your answer, >> I had a look to syslog and it seems that my server is already using rsyslog: > > <shrug> There isn't anything in the server that says "run faster in > debug mode". Usually it's the other way around, because of all the > extrea output that debug mode has. > >> I also try to print directly on stdout : >> destination = stdout >> Or in files >> And this doesn't realy change anything. > > Then the problem is elsewhere. > >> I also tried to reduce logging as much as possible for example by commenting >> : >> #auth_log >> but it doesn't realy help too. >> >> Looking forward to any clue that will help me to reduce this response time, > > What have you changed from the default configuration? Start looking > there. > > Alan DeKok. > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
