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. <div><br></div><div>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</div>
<div><br></div><div>-Brett</div><div><br></div><div><br><div><br><div class="gmail_quote">On Sun, Jun 14, 2009 at 1:06 PM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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.<br>
<br>
Regards,<br>
Bogdan<br>
<br>
Brett Nemeroff wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
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.<br>
<br>
<br></div><div class="im">
On Thu, Jun 11, 2009 at 3:28 AM, Bogdan-Andrei Iancu <<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a> <mailto:<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a>>> wrote:<br>
<br>
Saúl Ibarra wrote:<br>
>> Each OpenSIPS process opens at startup a mysql connection and<br>
it keeps it<br>
>> open till the shutdown - so the connection is persistent at<br>
runtime. Of<br>
>> course, a conection can be re-established at runtime if some<br>
connection lost<br>
>> event happens (timesout etc).<br>
>><br>
>><br>
><br>
> That's good to know :) But don't you think it's a bit risky to<br>
rely on<br>
> temporary tables in this case? If by any chance the connection<br>
is lost<br>
> strange things ca start to happen :-O ? I'd go for memcache ;)<br>
><br>
well, opensips takes care of its internal DB stuff (like re-init the<br>
prepared statements after a reconnect), but for other things you do by<br>
yourself from script, you need to take care by yourself :)<br>
<br>
But yes, the memcache is a good option :). especially that we are<br>
working on interfacing the memcache interface with the memcached<br>
daemon ;)<br>
<br>
Regards,<br>
Bogdan<br>
<br>
_______________________________________________<br>
Users mailing list<br></div>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a> <mailto:<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>><div class="im"><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
</div></blockquote>
<br>
</blockquote></div><br></div></div>