[OpenSIPS-Users] OpenSIPS and 256 MByte of RAM.

[Răzvan Crainea]

Hi, Rodrigo!

OpenSIPS by itself performs very well :). However, in a call, OpenSIPS 
is not all by itself: you need SIP clients, databases, DNS, and so forth 
and so on. In order to have better performance, you have to increase 
performance for each of these components. So you need to define what 
exactly is drawing OpenSIPS back: is it the processing itself, is it the 
database, is it the DNS and so on.

In order to pinpoint the components that have poor performance, OpenSIPS 
provides some thresholds that you can use to measure different stuff in 
the script, such as DNS queries[1], message processing [2] or mysql 
queries[3]. You should try to profile each of these and figure out what 
exactly is happening in your platform, to find out what exactly you 
can/should improve.

[1] http://www.opensips.org/Documentation/Script-CoreParameters-2-3#toc59
[2] http://www.opensips.org/Documentation/Script-CoreParameters-2-3#toc60
[3] http://www.opensips.org/html/docs/modules/2.3.x/db_mysql.html#id248019

Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 03/22/2017 03:12 PM, Rodrigo Pimenta Carvalho wrote:
>
> Hi.
>
>
> I was getting some problems with OpenSIPS and its performance in a 
> hardware with 1 CPU and 256 MByte of RAM.
>
> When I moved my OpenSIPS to another hardware with 2 CPUs and 516 MByte 
> of RAM it became working very well !
>
> But, I have to move back my OpenSIPS to the 'poor' hardware!
>
>
> So, what configurations in OpenSIPS files should I set, to get better 
> performance?
>
>
> Any suggestion will be very helpful!
>
>
> Best regards.
>
>
>
>
> RODRIGO PIMENTA CARVALHO
> Inatel Competence Center
> Software
> Ph: +55 35 3471 9200 RAMAL 979
>
>
> _______________________________________________
> 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/20170322/b3867384/attachment.html>