[asterisk-dev] 1.4 and CDRs -- The Breaking Point

[Venefax]

I can reconnect the old code if you and Steve Murphy want to set up some
debugs in the code and see if we can catch the issue. It is very easy to
reproduce. I have two dialplans, one with AGI and Perl and the other using
func_odbc.
Federico

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Sergey Okhapkin
Sent: Sunday, February 08, 2009 11:28 AM
To: asterisk-dev at lists.digium.com
Cc: Tilghman Lesher
Subject: Re: [asterisk-dev] 1.4 and CDRs -- The Breaking Point

On Sunday 08 February 2009, Tilghman Lesher wrote:
> > I have the same problem with mysql. I use func_odbc (backport form 1.6)
> > in dialplan and asterisk chokes when call rate reaches 20-25 calls per
> > second. CPU usage on quad core mysql box never exceeds 100%, seems like
> > queries on pooled connections are executed sequentially but not in
> > parallel.
>
> How are you backporting?  Are you using the backport on svncommunity, or
> did you roll your own? 

I use svncommunity backport.

> Are you using the pooling feature to request 
> multiple connections, or are you using a single shared connection? 

Connection pool is turned on in res_odbc.conf:

[a2billing]
enabled => yes
dsn => a2billing
username => xxxxxx
password => xxxxxx
pre-connect => yes
pooling => yes
limit => 50
idlecheck => 3600

> Also, what is it about the backport that made you choose to use it, rather
> than the func_odbc that is in 1.4?

I need separate read and write handles to run selects on local mysql slave
and 
send updates to mysql master. Also I use multiple read and write handles for

failover, these features are missed in 1.4.

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev