Documentation

Documentation.TroubleShooting-IncreaseMem History

Hide minor edits - Show changes to markup

August 06, 2014, at 04:05 PM by 12.160.0.155 -
Deleted lines 66-71:

(:nl:)>>messagehead<<

crorkz?06 August 2014, 12:19

J1pq9h wow, awesome blog. Much obliged.

August 06, 2014, at 12:19 PM by crorkz - Comment added
Added lines 67-72:

(:nl:)>>messagehead<<

crorkz?06 August 2014, 12:19

J1pq9h wow, awesome blog. Much obliged.

November 01, 2013, at 11:03 AM by bogdan -
Deleted lines 66-71:

(:nl:)>>messagehead<<

link building?01 November 2013, 04:17

ISgefr Really enjoyed this post.Really looking forward to read more. Really Cool.

November 01, 2013, at 04:17 AM by link building - Comment added
Added lines 67-72:

(:nl:)>>messagehead<<

link building?01 November 2013, 04:17

ISgefr Really enjoyed this post.Really looking forward to read more. Really Cool.

October 30, 2013, at 09:19 AM by 109.99.235.212 -
Changed line 1 from:

Documentation -> TroubleShooting -> Increasing Memory

to:

Documentation -> TroubleShooting -> Increasing Memory

May 09, 2013, at 01:52 PM by 79.118.227.150 -
Changed line 1 from:
to:

Documentation -> TroubleShooting -> Increasing Memory

May 09, 2013, at 01:46 PM by 79.118.227.150 -
Changed lines 1-2 from:

Resources -> Documentation -> Increasing Memory

to:
April 24, 2013, at 06:24 PM by 213.233.101.41 -
Added lines 1-67:

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:)


Page last modified on August 06, 2014, at 04:05 PM