I am auditing an existing opensips.cfg script trying to identify all possible places where a database query is executed. The purpose is to optimise performance by reducing the number of DB queries and eliminating any unnecessary synchronous database queries.
I would like to know more about what happens when the script calls the proxy_authorize() function. I assume it must be querying the subscriber table, but is this a synchronous query? Does the AUTH_DB module do any caching of data or will it always read directly from the DB table? Is there any difference between v2.4 and v3.1 here? Is there anything on the roadmap that may be relevant? The behaviour of proxy_authorize() could be relevant to system performance and reliability in the following situations: - An OpenSIPS system under heavy load with many call attempts per second - Where an unexpected network or DB-server issue results in slow DB query responses - potentially crashing OpenSIPS - If a "rogue" customer device or malicious hacking attempt generates large numbers of requests which all call proxy_authorize() John Quick Smartvox Limited _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
