Resources.DocsTsInm History

Hide minor edits - Show changes to markup

April 24, 2013, at 06:25 PM by 213.233.101.41 -
Changed lines 1-67 from:

Resources -> Documentation -> Increasing Memory

How to increase the memory that will be used by OpenSIPS?

Increase Private Memory Size

OpenSIPS has its own memory manager. Even if you have lot of memory in the system, OpenSIPS will use only the memory size it was configured, and you may get "out of memory" errors sooner than expected. This does not mean that there is a memory leak, but insufficient allocated size for your subscriber population. Common cases for large needs of private memory are: loading user location contacts, doing NAT pinging. Actual OpenSIPS versions overcome the first issue by implementing database FETCH support. The other cases will be taken in consideration very soon.

By default the size of private memory chunk used by each OpenSIPS process is 1 MB.

To increase the size of private memory you need to compile OpenSIPS from sources. Once you get the sources from SVN or the opensips.org's download site, do the following steps:

- edit the file "config.h" and search for the next lines:

  /*used only if PKG_MALLOC is defined*/
  #define PKG_MEM_POOL_SIZE 1024*1024

- change the value of PKG_MEM_POOL_SIZE to desired size, for example to have 4MB of private memory:

  #define PKG_MEM_POOL_SIZE 4*1024*1024

- recompile and reinstall OpenSIPS

  make all; make install;

In OpenSIPS 1.8 and higher you can increase the private memory size without recompiling, by passing the -M parameter at OpenSIPS startup. :

opensips -M 8

# this will run OpenSIPS with 8 MB of private memory per process

Increase Share Memory Size

To increase the share memory size use '-m' command line parameter of OpenSIPS.

opensips -m 256

# this will run OpenSIPS with 256MB of share memory

(:nl:)>>messagehead<<

Manas?12 November 2010, 14:49

If you installed Opensips via an RPM on RHEL/CentOS.

You will need to change this value in /etc/init.d/opensips script.

MEMORY=1024 #configured 1 G

MEMORY=$((`echo $MEMORY | sed -e 's/[^0-9]//g'`)) [ -z "$USER" ] && USER=opensips [ -z "$GROUP" ] && GROUP=opensips [ $MEMORY -le 0 ] && MEMORY=32

(:commentboxchrono:)

to:

(:redirect Documentation.TroubleShooting-IncreaseMem quiet=1 :)

April 11, 2013, at 11:30 AM by bogdan -
Deleted lines 65-70:

(:nl:)>>messagehead<<

Shakti?10 April 2013, 06:32

>I love to go to your blog page and see what is going on with Matt and Kelly (even when we are included in some piuctres I love your comments).Please keep this up!Best, Sandy

April 10, 2013, at 06:32 AM by Shakti - Comment added
Added lines 66-71:

(:nl:)>>messagehead<<

Shakti?10 April 2013, 06:32

>I love to go to your blog page and see what is going on with Matt and Kelly (even when we are included in some piuctres I love your comments).Please keep this up!Best, Sandy

December 07, 2012, at 11:28 AM by vlad_paiu -
Added lines 27-34:

In OpenSIPS 1.8 and higher you can increase the private memory size without recompiling, by passing the -M parameter at OpenSIPS startup. :

opensips -M 8

# this will run OpenSIPS with 8 MB of private memory per process
October 22, 2012, at 01:18 PM by bogdan -
Deleted lines 57-62:

(:nl:)>>messagehead<<

Ismaila?22 October 2012, 11:23

if your sis' machine comes with just 128 megs, i doubt wehehtr it IS a new one .before you add memory into a computer, check for the following things:whether the memory type is compatible- wehehtr it is sd ram, ddram, again wehehtr it is ddr1, ddr2 or ddr3.DONT EVER MIX THESE TYPES. THEY WONT MATCH. in case it is new, it will be a ddr2 or mostly a ddr3. so add only an identical module.whether the motherboard can support it- some motherboards can support upto only 4gb,etc.whether you mix and match the old and the new one.it is better if you remove the 128mb ram module while adding a new one. even though the system will recognize it, the machine performance will not be exactly the same, to some extent.also, a 128mb will be very tiny addition to a 2 or a 4gb module.you can check this all with the help of a computer expert nearby.hope this will help anyway.

October 22, 2012, at 11:23 AM by Ismaila - Comment added
Added lines 58-63:

(:nl:)>>messagehead<<

Ismaila?22 October 2012, 11:23

if your sis' machine comes with just 128 megs, i doubt wehehtr it IS a new one .before you add memory into a computer, check for the following things:whether the memory type is compatible- wehehtr it is sd ram, ddram, again wehehtr it is ddr1, ddr2 or ddr3.DONT EVER MIX THESE TYPES. THEY WONT MATCH. in case it is new, it will be a ddr2 or mostly a ddr3. so add only an identical module.whether the motherboard can support it- some motherboards can support upto only 4gb,etc.whether you mix and match the old and the new one.it is better if you remove the 128mb ram module while adding a new one. even though the system will recognize it, the machine performance will not be exactly the same, to some extent.also, a 128mb will be very tiny addition to a 2 or a 4gb module.you can check this all with the help of a computer expert nearby.hope this will help anyway.

May 13, 2011, at 11:38 AM by 109.99.2.142 - Comments Cleanup
Deleted lines 57-62:

(:nl:)>>messagehead<<

Tambrey?12 May 2011, 22:22

At last, smoeone comes up with the "right" answer!

May 12, 2011, at 10:22 PM by Tambrey - Comment added
Added lines 58-63:

(:nl:)>>messagehead<<

Tambrey?12 May 2011, 22:22

At last, smoeone comes up with the "right" answer!

May 12, 2011, at 11:26 AM by bogdan - Comments Cleanup
Deleted lines 57-67:

(:nl:)>>messagehead<<

Lynell?11 May 2011, 16:08

Wow! That's a ralely neat answer!

(:nl:)>>messagehead<<

Kaycie?12 May 2011, 04:31

Hey, stuble must be your middle name. Great post!

May 12, 2011, at 04:31 AM by Kaycie - Comment added
Added lines 62-67:

(:nl:)>>messagehead<<

Kaycie?12 May 2011, 04:31

Hey, stuble must be your middle name. Great post!

May 11, 2011, at 04:08 PM by Lynell - Comment added
Added lines 56-61:

(:nl:)>>messagehead<<

Lynell?11 May 2011, 16:08

Wow! That's a ralely neat answer!

November 12, 2010, at 02:49 PM by Manas - Comment added
Added lines 40-56:

(:nl:)>>messagehead<<

Manas?12 November 2010, 14:49

If you installed Opensips via an RPM on RHEL/CentOS.

You will need to change this value in /etc/init.d/opensips script.

MEMORY=1024 #configured 1 G

MEMORY=$((`echo $MEMORY | sed -e 's/[^0-9]//g'`)) [ -z "$USER" ] && USER=opensips [ -z "$GROUP" ] && GROUP=opensips [ $MEMORY -le 0 ] && MEMORY=32

June 03, 2010, at 09:48 PM by bogdan -
Changed lines 1-41 from:

m71hGQ <a href="http://kvvmmcjyozwg.com/">kvvmmcjyozwg</a>, [url=http://zyflzhiusouo.com/]zyflzhiusouo[/url], [link=http://wwjfemquxtjp.com/]wwjfemquxtjp[/link], http://eycypffteukj.com/

to:

Resources -> Documentation -> Increasing Memory

How to increase the memory that will be used by OpenSIPS?

Increase Private Memory Size

OpenSIPS has its own memory manager. Even if you have lot of memory in the system, OpenSIPS will use only the memory size it was configured, and you may get "out of memory" errors sooner than expected. This does not mean that there is a memory leak, but insufficient allocated size for your subscriber population. Common cases for large needs of private memory are: loading user location contacts, doing NAT pinging. Actual OpenSIPS versions overcome the first issue by implementing database FETCH support. The other cases will be taken in consideration very soon.

By default the size of private memory chunk used by each OpenSIPS process is 1 MB.

To increase the size of private memory you need to compile OpenSIPS from sources. Once you get the sources from SVN or the opensips.org's download site, do the following steps:

- edit the file "config.h" and search for the next lines:

  /*used only if PKG_MALLOC is defined*/
  #define PKG_MEM_POOL_SIZE 1024*1024

- change the value of PKG_MEM_POOL_SIZE to desired size, for example to have 4MB of private memory:

  #define PKG_MEM_POOL_SIZE 4*1024*1024

- recompile and reinstall OpenSIPS

  make all; make install;

Increase Share Memory Size

To increase the share memory size use '-m' command line parameter of OpenSIPS.

opensips -m 256

# this will run OpenSIPS with 256MB of share memory

(:commentboxchrono:)

June 03, 2010, at 05:28 PM by vfjauekl - 1048576
Changed line 1 from:

vMQ0oF <a href="http://fgqrdwruifuk.com/">fgqrdwruifuk</a>, [url=http://mvnluhypfycp.com/]mvnluhypfycp[/url], [link=http://puwiypsyqogn.com/]puwiypsyqogn[/link], http://wynwbfmreaiq.com/

to:

m71hGQ <a href="http://kvvmmcjyozwg.com/">kvvmmcjyozwg</a>, [url=http://zyflzhiusouo.com/]zyflzhiusouo[/url], [link=http://wwjfemquxtjp.com/]wwjfemquxtjp[/link], http://eycypffteukj.com/

June 03, 2010, at 03:34 PM by vfossm - 1048576
Changed line 1 from:

jBwtmZ <a href="http://yhpmjqipjlnf.com/">yhpmjqipjlnf</a>, [url=http://vddibbwrlxuw.com/]vddibbwrlxuw[/url], [link=http://wocffwwddlvx.com/]wocffwwddlvx[/link], http://ynuzcnzzlbfx.com/

to:

vMQ0oF <a href="http://fgqrdwruifuk.com/">fgqrdwruifuk</a>, [url=http://mvnluhypfycp.com/]mvnluhypfycp[/url], [link=http://puwiypsyqogn.com/]puwiypsyqogn[/link], http://wynwbfmreaiq.com/

June 03, 2010, at 01:36 PM by epgytruzepg - 1048576
Changed line 1 from:

GSMSQh <a href="http://bgergrhqfjga.com/">bgergrhqfjga</a>, [url=http://bgvqzehuomdz.com/]bgvqzehuomdz[/url], [link=http://cfzweeuwlkzs.com/]cfzweeuwlkzs[/link], http://ofjmoznjdmft.com/

to:

jBwtmZ <a href="http://yhpmjqipjlnf.com/">yhpmjqipjlnf</a>, [url=http://vddibbwrlxuw.com/]vddibbwrlxuw[/url], [link=http://wocffwwddlvx.com/]wocffwwddlvx[/link], http://ynuzcnzzlbfx.com/

June 03, 2010, at 01:27 PM by badcsggobt - GTRqTimZRemmcW
Changed line 1 from:

wBP9sj <a href="http://qrvgjduimkyp.com/">qrvgjduimkyp</a>, [url=http://wqxipetheqvn.com/]wqxipetheqvn[/url], [link=http://cbxnkpoyuhbs.com/]cbxnkpoyuhbs[/link], http://wrshnbankmie.com/

to:

GSMSQh <a href="http://bgergrhqfjga.com/">bgergrhqfjga</a>, [url=http://bgvqzehuomdz.com/]bgvqzehuomdz[/url], [link=http://cfzweeuwlkzs.com/]cfzweeuwlkzs[/link], http://ofjmoznjdmft.com/

June 03, 2010, at 12:30 PM by nwaogmyb - 1048576
Changed lines 1-41 from:

Resources -> Documentation -> Increasing Memory

How to increase the memory that will be used by OpenSIPS?

Increase Private Memory Size

OpenSIPS has its own memory manager. Even if you have lot of memory in the system, OpenSIPS will use only the memory size it was configured, and you may get "out of memory" errors sooner than expected. This does not mean that there is a memory leak, but insufficient allocated size for your subscriber population. Common cases for large needs of private memory are: loading user location contacts, doing NAT pinging. Actual OpenSIPS versions overcome the first issue by implementing database FETCH support. The other cases will be taken in consideration very soon.

By default the size of private memory chunk used by each OpenSIPS process is 1 MB.

To increase the size of private memory you need to compile OpenSIPS from sources. Once you get the sources from SVN or the opensips.org's download site, do the following steps:

- edit the file "config.h" and search for the next lines:

  /*used only if PKG_MALLOC is defined*/
  #define PKG_MEM_POOL_SIZE 1024*1024

- change the value of PKG_MEM_POOL_SIZE to desired size, for example to have 4MB of private memory:

  #define PKG_MEM_POOL_SIZE 4*1024*1024

- recompile and reinstall OpenSIPS

  make all; make install;

Increase Share Memory Size

To increase the share memory size use '-m' command line parameter of OpenSIPS.

opensips -m 256

# this will run OpenSIPS with 256MB of share memory

(:commentboxchrono:)

to:

wBP9sj <a href="http://qrvgjduimkyp.com/">qrvgjduimkyp</a>, [url=http://wqxipetheqvn.com/]wqxipetheqvn[/url], [link=http://cbxnkpoyuhbs.com/]cbxnkpoyuhbs[/link], http://wrshnbankmie.com/

February 18, 2010, at 11:11 AM by bogdan - Post removed - only English accepted.
Deleted lines 39-44:

(:nl:)>>messagehead<<

Lunita?25 October 2009, 15:53

Deseo saber los requerimientos ínimos y recomendados para instalar y configurar un servidor con Opensip. Y si se trata de una integración con Asterisk serían los mismos requerimientos.

October 25, 2009, at 03:53 PM by Lunita - Comment added
Added lines 40-46:

(:nl:)>>messagehead<<

Lunita?25 October 2009, 15:53

Deseo saber los requerimientos ínimos y recomendados para instalar y configurar un servidor con Opensip. Y si se trata de una integración con Asterisk serían los mismos requerimientos.

March 03, 2009, at 10:47 AM by bogdan -
Changed lines 37-40 from:

@]

to:

@]


(:commentboxchrono:)

August 02, 2008, at 10:24 PM by 92.80.65.247 -
Changed line 4 from:

Hoe to increase the memory that will be used by OpenSIPS?

to:

How to increase the memory that will be used by OpenSIPS?

August 02, 2008, at 10:24 PM by 92.80.65.247 -
Added lines 1-6:

Resources -> Documentation -> Increasing Memory

Hoe to increase the memory that will be used by OpenSIPS?

August 02, 2008, at 10:20 PM by 92.80.65.247 -
Added lines 1-31:

Increase Private Memory Size

OpenSIPS has its own memory manager. Even if you have lot of memory in the system, OpenSIPS will use only the memory size it was configured, and you may get "out of memory" errors sooner than expected. This does not mean that there is a memory leak, but insufficient allocated size for your subscriber population. Common cases for large needs of private memory are: loading user location contacts, doing NAT pinging. Actual OpenSIPS versions overcome the first issue by implementing database FETCH support. The other cases will be taken in consideration very soon.

By default the size of private memory chunk used by each OpenSIPS process is 1 MB.

To increase the size of private memory you need to compile OpenSIPS from sources. Once you get the sources from SVN or the opensips.org's download site, do the following steps:

- edit the file "config.h" and search for the next lines:

  /*used only if PKG_MALLOC is defined*/
  #define PKG_MEM_POOL_SIZE 1024*1024

- change the value of PKG_MEM_POOL_SIZE to desired size, for example to have 4MB of private memory:

  #define PKG_MEM_POOL_SIZE 4*1024*1024

- recompile and reinstall OpenSIPS

  make all; make install;

Increase Share Memory Size

To increase the share memory size use '-m' command line parameter of OpenSIPS.

opensips -m 256

# this will run OpenSIPS with 256MB of share memory

Page last modified on April 24, 2013, at 06:25 PM