I am using 2.1.4 release. Are you saying that the latest release improved that? I did not change the default configuration. here is how it looks: authorize { ... eap { ok = return } ... sql } We see that it fetches data from database 4(radcheck,radusergroup,radgroupcheck,radgroupreply)*11 (handshake challenges) = 44 times for every EAP-TLS authentication leopold wrote:
Hello, Can anyone recommend improving performance for EAP-TLS when using SQL backend? Currently we see around 11 message exchanges (10 Access-Challenge messages from the server) for each EAP-TLS authentication and each time client sends data, the server tries to fetch data from database which is bad. This results in huge number of database lookups that kill performance.
What is recommended way to deal with such problem? Thanks
-- View this message in context: http://www.nabble.com/EAP-TLS-performance-SQL-backend-bottleneck-tp25386668p... Sent from the FreeRadius - User mailing list archive at Nabble.com.