Hello Vic,
SIP tracing may be add a significant load on the DB (and on opensips
itself - as it is doing blocking DB ops) as for each message it has to
do 2 insert queries - and for a minimal call you around 10 inserts.
The idea is to minimize the traffic you trace (trace only what you need,
not all traffic) and to optimize the dumping to DB:
1) use the multi-insert option (see query_buffer_size -
http://www.opensips.org/Resources/DocsCoreFcn19#toc71)
2) consider using the flatstore DB engine (which is a write-only
very fast engine to write to files)
3) consider doing the DB ops on a different opensips instance than
the one handling the traffic (active opensips is just packing data and
another one is dumping into DB) - see Homer with sip_trace and
sip_capture modules.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 04/15/2013 10:37 PM, Vic Jolin wrote:
How much additional load is added when siptrace is turned on, but the
database server is different. Meaning I have a separate DB just for
doing sip traces.
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
