Well, is Perl DBI thread-safe for a start??? -----Original Message----- From: Leo Ann Boon [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 11, 2006 5:32 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Nested MySQL Commands
Douglas Garstang wrote: >So I really wish there was some way to measure how well the worst case >scenario would perform. This would be 120 simultaneous calls (don't know how >many per second) on a Dual 3.8Ghz Dell PowerEdge 1850 with 2GB RAM. Asterisk >would call an AGI script, written in perl, to route all calls. The script >would have to perform multiple database queries in order to route a call. > > Why don't you use FastAGI? Run the lookup 'script' as a standalone application communicating with Asterisk through sockets. Once you're decoupled from the process forking model, you can implement all those nifty thread, connection pooling tricks. You'll probably need to use stored procedures on the SQL side. You should also do some traffic modeling to optimize the resource planning. I don't really think you need 120 threads to handle the load. In traditional PBX, when using host-based routing (or so-called adjunct routing) you get a grace period of about 4 seconds to route the call. Time to dig out the erlang-c calculator :). _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
