Hi Brett,

Brett Nemeroff wrote:
Ok, well I'll try this out for performance. I'm curious to see what I'd be able to handle doing live mysql routing decisions with all the new prepared statements and such.
note that not all the DB ops are using prepared statements - most of the modules do use it internally, but when running raw queries (with avp_db_query() ), the query will be done in old fashion text one.

Of course, I'm a big proponent of doing memory routing, but I may need some capabilities to route based on other factors such as ASR and PDD to automatically set the route priorities. Maybe a module someday.. :D
can you share some ideas ? :D

Regards,
Bogdan

-Brett



On Sun, Jun 14, 2009 at 1:06 PM, Bogdan-Andrei Iancu <[email protected] <mailto:[email protected]>> wrote:

    hard to say - to be honest I never used "temporary" tables - I
    just commented from the opensips point of view, on how the mysql
    connections are managed.

    Regards,
    Bogdan

    Brett Nemeroff wrote:

        Ok, so basically I build a temp table called "routes" from a
        stored proc. Can I not rely on this being a unique table per
        transaction if the session is held alive? Of course I could
        name the table something like routes_<timestamp>_<$ru> and
        trash it at the end of the stored proc. I just don't want to
        end up with a race condition.


        On Thu, Jun 11, 2009 at 3:28 AM, Bogdan-Andrei Iancu
        <[email protected] <mailto:[email protected]>
        <mailto:[email protected]
        <mailto:[email protected]>>> wrote:

           Saúl Ibarra wrote:
           >> Each OpenSIPS process opens at startup a mysql
        connection and
           it keeps it
           >> open till the shutdown - so the connection is persistent at
           runtime. Of
           >> course, a conection can be re-established at runtime if some
           connection lost
           >> event happens (timesout etc).
           >>
           >>
           >
           > That's good to know :) But don't you think it's a bit
        risky to
           rely on
           > temporary tables in this case? If by any chance the
        connection
           is lost
           > strange things ca start to happen :-O ? I'd go for
        memcache ;)
           >
           well, opensips takes care of its internal DB stuff (like
        re-init the
           prepared statements after a reconnect), but for other
        things you do by
           yourself from script, you need to take care by yourself :)

           But yes, the memcache is a good option :). especially that
        we are
           working on interfacing the memcache interface with the
        memcached
           daemon ;)

           Regards,
           Bogdan

           _______________________________________________
           Users mailing list
           [email protected] <mailto:[email protected]>
        <mailto:[email protected]
        <mailto:[email protected]>>

           http://lists.opensips.org/cgi-bin/mailman/listinfo/users





_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to