Hi Nash,
It is somewhere in the middle :). Of course the DB ops will bring some
penalties to the performance, so you need to take care and tune your DB
for the best performance (not to drag down opensips). With db ops is
very common in OpenSIPS scripts, so you do not do anything crazy or
stupid there.
Of course, you should look into optimizing the DB ops you use:
- DB auth - use caching at script level (see
http://www.opensips.org/Documentation/Tutorials-MemoryCaching)
- ACC - consider using db_flatstore to avoid writing into a real DB
- dialog - if not really a must use db modes 2 or 3
(http://www.opensips.org/html/docs/modules/1.11.x/dialog.html#id294001)
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 09.01.2015 20:19, John Nash wrote:
I have used opensips for load balancing and some border proxy+
NAT+rtpproxy in past and am quite happy with it. Recently I decided to
add DB operations (Auth and accounting, routing and dialog into it so
that heavy lifting of VOIP network can be given to opensips. I wanted
to send call to PBX only when it is really needed (Like voicemail and
conference etc)
But in a long time I saw this article
http://www.opensips.org/Documentation/TroubleShooting-FindPerfPb
As per this tutorial I think if any DB operation is slow, it will hit
overall performance (I mean the transactions which do not require DB
can also be stuck).
I know good engineers at openisps have already figured it out and
working on 2.X version but looks like it will take a while so that I
can give it a try (As dialog is not in current release).
With 1.X series + DB auth/acc + dialog should I reconsider my approach
or there are systems running successfully and I am just being paranoid?
John
_______________________________________________
Users mailing list
[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
