[OpenSIPS-Users] Solution to storing a lot of siptrace

Arsen arsen.semionov at gmail.com
Fri Dec 8 15:43:23 EST 2017


+1 for Homer. Nosql also seems a good idea.



Arsen Semionov
www.eurolan.info
cell: +442035198881

On Fri, Dec 8, 2017 at 10:21 PM, Jon Abrams <ffshoh at gmail.com> wrote:

> You might try using TokuDB table storage for MySql/MariaDB without
> compression. The penalty for indexing is much reduced over InnoDB.
>
> You might also replicate the sip traces off your live proxy to another
> OpenSIPs capture node and let that node handle the inserts. Take a look at
> Web Homer as well.
>
> On Fri, Dec 8, 2017 at 1:43 PM, Daniel Zanutti <daniel.zanutti at gmail.com>
> wrote:
>
>> Hi
>>
>> I have around 2000 simultaneous calls, 50 CPS and would like to store sip
>> trace for all of them.
>>
>> Storing on MySQL is not working. If you have some indexes on the table,
>> after 1M register it starts to slow down the whole server. If no indexes,
>> it's not searchable.
>>
>> Do you guys have a good solution to store a lot of sip trace on Opensips?
>> Like 200 GB.
>>
>> It needs to be searchable almost real-time (a few minutes is fine).
>>
>> I was thinking on store on a flat text file and move to a NOSQL solution,
>> what do you guys think?
>>
>> Thanks
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20171208/f4fa4e9f/attachment.html>


More information about the Users mailing list