We’re starting to investigate moving rlm_sql to the new async I/O model. The main benefits being: - Significant increase in TPS where DB benefits from increased parallelism, or RTT to the database is high. - FreeRADIUS no longer appears to “hang” when databases go away (it doesn’t actually hang, but all the worker threads get tied up until they time out). - In the hanging (not hanging) scenario, we can drain the incoming packet queue to detail files without “hiccups” (where the inbound packet queue fills) waiting for stale connections to close or queries to time out. Ongoing discussion on GitHub is here: https://github.com/FreeRADIUS/freeradius-server/issues/1913 Questions for users are: - Does anyone still use DB2? It’s virtually undocumented and it’s not clear if it has an async interface. - Does anyone still use Firebird? Is there any disadvantage in using it via ODBC. - Is there still value in maintaining IODBC compatibility? It seems to lack many features of UnixODBC. Previously IODBC was included in OSX Lion, so it was useful to keep around. It’s since been removed however, and UnixODBC can be installed with hombrew. -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2