[Asterisk-Users] Re: Nested MySQL Commands
Mike Fedyk
mfedyk at mikefedyk.com
Wed Jan 11 16:32:16 MST 2006
Tony Mountifield wrote:
>In article <645FEC31A18FE54A8721500CDD55A7B602B425B7 at mail.oneeighty.com>,
>Douglas Garstang <dgarstang at oneeighty.com> wrote:
>
>
>>Peter,
>>
>>Too slow! We're going to potentially be doing several MySQL lookups for routing even the
>>most basic of calls, and if every one of those queries has to make a call out to an AGI
>>script, it would become a performance problem.
>>
>>
>
>AGI is only slow if you're calling it repeatedly and implementing it in
>a scripting language that needs a big interpreter.
>
>I have had great success writing AGIs in C and interfacing to MySQL
>from within them. They end up nice and small and fast. A single AGI
>invocation does all the database transactions necessary to decide
>on the disposition of the call, and then jumps to the appropriate
>extension and priority in the dialplan.
>
And if you like writing your AGIs in interpreted languages, there is
always FastAGI.
More information about the asterisk-users
mailing list