Hi
1. Is there any benefit of increasing the value of PKG_MEM_POOL_SIZE and SHM_MEM_SIZE ?
/*used only if PKG_MALLOC is defined*/ #define PKG_MEM_POOL_SIZE 1024*1024
/*used if SH_MEM is defined*/ #define SHM_MEM_SIZE 32
2. I've compiled my ser with
#define PKG_MEM_POOL_SIZE 1024*1024*512
ans started using ser -m 100 option with children=4 and listening on two ips
when I started memory usages was seems to fine for few days(3-4) less then 1GB but after that nealy 1.7 - 1.8 GB of memory usage and when I do top:
16165 root 15 0 617m 54m 36m S 0.3 2.7 0:16.34 ser 16167 root 15 0 617m 54m 36m S 0.3 2.7 0:15.89 ser 16164 root 15 0 617m 54m 36m S 0.3 2.7 0:16.29 ser 16166 root 15 0 617m 54m 36m S 0.7 2.7 0:16.16 ser 16172 root 16 0 617m 53m 35m S 0.0 2.7 0:05.04 ser 16168 root 16 0 617m 52m 34m S 0.0 2.6 0:00.09 ser 16170 root 16 0 617m 52m 34m S 0.0 2.6 0:00.07 ser 16169 root 16 0 617m 52m 34m S 0.0 2.6 0:00.08 ser 16171 root 16 0 617m 52m 34m S 0.0 2.6 0:00.10 ser 16163 root 16 0 617m 52m 34m S 0.0 2.6 0:00.01 ser 16145 root 25 0 617m 52m 34m S 0.0 2.6 0:07.80 ser
it shows 11 instance of ser with above info. If I sum up 617 * 11 = 6787 MB of memory but in my machine I've only 2 GB Physical RAM and it never uses Swap ? if 54 * 11 = 594 ? but free -m and top shows more memory usage ?
can please explain me in brief . I'll be really thankfull. B'coz of this I'm facing may problem.
thanks
arun
The numbers shown for memory usage also include shared memory, ie memory used by multiple processes/threads, these shared areas will be counted multiple times.
Use `free` to find the real amount of used memory on your server (look at the +/- buffers section)
________________________________
From: users-bounces@openser.org [mailto:users-bounces@openser.org] On Behalf Of Arun Kumar Sent: 20 June 2007 14:44 To: USER; serusers@lists.iptel.org Subject: [Users] regarding memory usage
Hi
1. Is there any benefit of increasing the value of PKG_MEM_POOL_SIZE and SHM_MEM_SIZE ?
/*used only if PKG_MALLOC is defined*/ #define PKG_MEM_POOL_SIZE 1024*1024
/*used if SH_MEM is defined*/ #define SHM_MEM_SIZE 32
2. I've compiled my ser with
#define PKG_MEM_POOL_SIZE 1024*1024*512
ans started using ser -m 100 option with children=4 and listening on two ips
when I started memory usages was seems to fine for few days(3-4) less then 1GB but after that nealy 1.7 - 1.8 GB of memory usage and when I do top:
16165 root 15 0 617m 54m 36m S 0.3 2.7 0:16.34 ser 16167 root 15 0 617m 54m 36m S 0.3 2.7 0:15.89 ser 16164 root 15 0 617m 54m 36m S 0.3 2.7 0:16.29 ser 16166 root 15 0 617m 54m 36m S 0.7 2.7 0:16.16 ser 16172 root 16 0 617m 53m 35m S 0.0 2.7 0:05.04 ser 16168 root 16 0 617m 52m 34m S 0.0 2.6 0:00.09 ser 16170 root 16 0 617m 52m 34m S 0.0 2.6 0:00.07 ser 16169 root 16 0 617m 52m 34m S 0.0 2.6 0:00.08 ser 16171 root 16 0 617m 52m 34m S 0.0 2.6 0:00.10 ser 16163 root 16 0 617m 52m 34m S 0.0 2.6 0:00.01 ser 16145 root 25 0 617m 52m 34m S 0.0 2.6 0:07.80 ser
it shows 11 instance of ser with above info. If I sum up 617 * 11 = 6787 MB of memory but in my machine I've only 2 GB Physical RAM and it never uses Swap ? if 54 * 11 = 594 ? but free -m and top shows more memory usage ?
can please explain me in brief . I'll be really thankfull. B'coz of this I'm facing may problem.
thanks
arun
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
# free total used free shared buffers cached Mem: 2074376 1740724 333652 0 72328 1280192 -/+ buffers/cache: 388204 1686172 Swap: 2031608 0 2031608
can you please explain in brief all the info.
thanks arun
On 6/20/07, Morgan Gilroy morgan@telappliant.com wrote:
The numbers shown for memory usage also include shared memory, ie memory used by multiple processes/threads, these shared areas will be counted multiple times.
Use `free` to find the real amount of used memory on your server (look at the +/- buffers section)
*From:* users-bounces@openser.org [mailto:users-bounces@openser.org] *On Behalf Of *Arun Kumar *Sent:* 20 June 2007 14:44 *To:* USER; serusers@lists.iptel.org *Subject:* [Users] regarding memory usage
Hi
- Is there any benefit of increasing the value of PKG_MEM_POOL_SIZE and
SHM_MEM_SIZE ?
/*used only if PKG_MALLOC is defined*/ #define PKG_MEM_POOL_SIZE 1024*1024
/*used if SH_MEM is defined*/ #define SHM_MEM_SIZE 32
- I've compiled my ser with
#define PKG_MEM_POOL_SIZE 1024*1024*512
ans started using ser -m 100 option with children=4 and listening on two ips
when I started memory usages was seems to fine for few days(3-4) less then 1GB but after that nealy 1.7 - 1.8 GB of memory usage and when I do top:
16165 root 15 0 617m 54m 36m S 0.3 2.7 0:16.34 ser 16167 root 15 0 617m 54m 36m S 0.3 2.7 0:15.89 ser 16164 root 15 0 617m 54m 36m S 0.3 2.7 0:16.29 ser 16166 root 15 0 617m 54m 36m S 0.7 2.7 0:16.16 ser 16172 root 16 0 617m 53m 35m S 0.0 2.7 0:05.04 ser 16168 root 16 0 617m 52m 34m S 0.0 2.6 0:00.09 ser 16170 root 16 0 617m 52m 34m S 0.0 2.6 0:00.07 ser 16169 root 16 0 617m 52m 34m S 0.0 2.6 0:00.08 ser 16171 root 16 0 617m 52m 34m S 0.0 2.6 0:00.10 ser 16163 root 16 0 617m 52m 34m S 0.0 2.6 0:00.01 ser 16145 root 25 0 617m 52m 34m S 0.0 2.6 0:07.80 ser
it shows 11 instance of ser with above info. If I sum up 617 * 11 = 6787 MB of memory but in my machine I've only 2 GB Physical RAM and it never uses Swap ? if 54 * 11 = 594 ? but free -m and top shows more memory usage ?
can please explain me in brief . I'll be really thankfull. B'coz of this I'm facing may problem.
thanks
arun
This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
On Mittwoch, 20. Juni 2007, Arun Kumar wrote:
Hi
- Is there any benefit of increasing the value of PKG_MEM_POOL_SIZE and
SHM_MEM_SIZE ?
/*used only if PKG_MALLOC is defined*/ #define PKG_MEM_POOL_SIZE 1024*1024
/*used if SH_MEM is defined*/ #define SHM_MEM_SIZE 32
- I've compiled my ser with
#define PKG_MEM_POOL_SIZE 1024*1024*512
Hello Arun,
this is really to much private memory. You should not need more then 10 MB, even in quite large installations. Its much more reasonable to increase the shared memory parameter, e.g. to system memory / number of children.
Cheers,
Henning
hi
when I compiled with 10MB it give me this : 0(0) convert_row(): No memory left 0(0) convert_rows(): Error while converting row #62355 0(0) convert_result(): Error while converting rows 0(0) store_result(): Error while converting result 0(0) preload_udomain(): Error while doing db_query 0(0) register_udomain(): Error while preloading domain 'aliases' 0(0) release_connection(): Removing connection from the pool 0(0) domain_fixup(): Error while registering domain ERROR: error -1 while trying to fix configuration 0(0) XLOG: destroy module ... 0(0) DEBUG: tm_shutdown : start 0(0) DEBUG: unlink_timer_lists : emptying DELETE list 0(0) DEBUG: tm_shutdown : emptying hash table 0(0) DEBUG: tm_shutdown : releasing timers 0(0) DEBUG: tm_shutdown : removing semaphores 0(0) DEBUG: tm_shutdown : destroying tmcb lists 0(0) DEBUG: tm_shutdown : done 0(20330) shm_mem_destroy
thanks
On 6/21/07, Henning Westerholt henning.westerholt@1und1.de wrote:
On Mittwoch, 20. Juni 2007, Arun Kumar wrote:
Hi
- Is there any benefit of increasing the value
of PKG_MEM_POOL_SIZE and
SHM_MEM_SIZE ?
/*used only if PKG_MALLOC is defined*/ #define PKG_MEM_POOL_SIZE 1024*1024
/*used if SH_MEM is defined*/ #define SHM_MEM_SIZE 32
- I've compiled my ser with
#define PKG_MEM_POOL_SIZE 1024*1024*512
Hello Arun,
this is really to much private memory. You should not need more then 10 MB, even in quite large installations. Its much more reasonable to increase the shared memory parameter, e.g. to system memory / number of children.
Cheers,
Henning
Hello,
as said in the other email, I assume you are running an older version of openser and have a lot of location (aliases) entries. I paste from the other email:
Older versions used to load everything in private memory and then move to shared memory. With openser 1.2.x, that problem is gone, as it is using db fetch mechanism. Also, the server is no longer blocked during loading, as it is done by first child, the rest can handle sip traffic immediately at startup.
Just let me know the numbers in location/aliases to see a roughly estimation of required memory. The best is to migrate to 1.2.1, which solves this problem in a nice way, also is much faster in usrloc when dealing with large number of records.
http://www.openser.org/docs/openser-performance-tests/#ul-tests
Cheers, Daniel
On 06/21/07 12:00, Arun Kumar wrote:
hi
when I compiled with 10MB it give me this : 0(0) convert_row(): No memory left 0(0) convert_rows(): Error while converting row #62355 0(0) convert_result(): Error while converting rows 0(0) store_result(): Error while converting result 0(0) preload_udomain(): Error while doing db_query 0(0) register_udomain(): Error while preloading domain 'aliases' 0(0) release_connection(): Removing connection from the pool 0(0) domain_fixup(): Error while registering domain ERROR: error -1 while trying to fix configuration 0(0) XLOG: destroy module ... 0(0) DEBUG: tm_shutdown : start 0(0) DEBUG: unlink_timer_lists : emptying DELETE list 0(0) DEBUG: tm_shutdown : emptying hash table 0(0) DEBUG: tm_shutdown : releasing timers 0(0) DEBUG: tm_shutdown : removing semaphores 0(0) DEBUG: tm_shutdown : destroying tmcb lists 0(0) DEBUG: tm_shutdown : done 0(20330) shm_mem_destroy
thanks
On 6/21/07, *Henning Westerholt* <henning.westerholt@1und1.de mailto:henning.westerholt@1und1.de> wrote:
On Mittwoch, 20. Juni 2007, Arun Kumar wrote: > Hi > > 1. Is there any benefit of increasing the value of PKG_MEM_POOL_SIZE and > SHM_MEM_SIZE ? > > /*used only if PKG_MALLOC is defined*/ > #define PKG_MEM_POOL_SIZE 1024*1024 > > /*used if SH_MEM is defined*/ > #define SHM_MEM_SIZE 32 > > > 2. I've compiled my ser with > > #define PKG_MEM_POOL_SIZE 1024*1024*512 Hello Arun, this is really to much private memory. You should not need more then 10 MB, even in quite large installations. Its much more reasonable to increase the shared memory parameter, e.g. to system memory / number of children. Cheers, Henning
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
UsrLoc Stats Domain Registered Expired 'location' 325 2706 'aliases' 111841 0
On 6/21/07, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello,
as said in the other email, I assume you are running an older version of openser and have a lot of location (aliases) entries. I paste from the other email:
Older versions used to load everything in private memory and then move to shared memory. With openser 1.2.x, that problem is gone, as it is using db fetch mechanism. Also, the server is no longer blocked during loading, as it is done by first child, the rest can handle sip traffic immediately at startup.
Just let me know the numbers in location/aliases to see a roughly estimation of required memory. The best is to migrate to 1.2.1, which solves this problem in a nice way, also is much faster in usrloc when dealing with large number of records.
http://www.openser.org/docs/openser-performance-tests/#ul-tests
Cheers, Daniel
On 06/21/07 12:00, Arun Kumar wrote:
hi
when I compiled with 10MB it give me this : 0(0) convert_row(): No memory left 0(0) convert_rows(): Error while converting row #62355 0(0) convert_result(): Error while converting rows 0(0) store_result(): Error while converting result 0(0) preload_udomain(): Error while doing db_query 0(0) register_udomain(): Error while preloading domain 'aliases' 0(0) release_connection(): Removing connection from the pool 0(0) domain_fixup(): Error while registering domain ERROR: error -1 while trying to fix configuration 0(0) XLOG: destroy module ... 0(0) DEBUG: tm_shutdown : start 0(0) DEBUG: unlink_timer_lists : emptying DELETE list 0(0) DEBUG: tm_shutdown : emptying hash table 0(0) DEBUG: tm_shutdown : releasing timers 0(0) DEBUG: tm_shutdown : removing semaphores 0(0) DEBUG: tm_shutdown : destroying tmcb lists 0(0) DEBUG: tm_shutdown : done 0(20330) shm_mem_destroy
thanks
On 6/21/07, *Henning Westerholt* <henning.westerholt@1und1.de mailto:henning.westerholt@1und1.de> wrote:
On Mittwoch, 20. Juni 2007, Arun Kumar wrote: > Hi > > 1. Is there any benefit of increasing the value of PKG_MEM_POOL_SIZE and > SHM_MEM_SIZE ? > > /*used only if PKG_MALLOC is defined*/ > #define PKG_MEM_POOL_SIZE 1024*1024 > > /*used if SH_MEM is defined*/ > #define SHM_MEM_SIZE 32 > > > 2. I've compiled my ser with > > #define PKG_MEM_POOL_SIZE 1024*1024*512 Hello Arun, this is really to much private memory. You should not need more then 10 MB, even in quite large installations. Its much more reasonable to increase the shared memory parameter, e.g. to system memory / number of children. Cheers, Henning
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
On 06/21/07 12:24, Arun Kumar wrote:
UsrLoc Stats Domain Registered Expired 'location' 325 2706 'aliases' 111841 0
you have over 111000 aliases. That will require to have 32MB of private memory for each child. See the news when the issue was fixed http://www.openser.org/mos/view/News/NewsItem/Database-fetch-support/
Since then, lot of other improvements were done in user location. You really should migrate to 1.2.1 and get rid of such limitations and get better performances.
Alternative is to use alias_db for handling aliases. It won't load full aliases table in memory.
Cheers, Daniel
On 6/21/07, *Daniel-Constantin Mierla* < daniel@voice-system.ro mailto:daniel@voice-system.ro> wrote:
Hello, as said in the other email, I assume you are running an older version of openser and have a lot of location (aliases) entries. I paste from the other email: Older versions used to load everything in private memory and then move to shared memory. With openser 1.2.x, that problem is gone, as it is using db fetch mechanism. Also, the server is no longer blocked during loading, as it is done by first child, the rest can handle sip traffic immediately at startup. Just let me know the numbers in location/aliases to see a roughly estimation of required memory. The best is to migrate to 1.2.1, which solves this problem in a nice way, also is much faster in usrloc when dealing with large number of records. http://www.openser.org/docs/openser-performance-tests/#ul-tests Cheers, Daniel On 06/21/07 12:00, Arun Kumar wrote: > > hi > > when I compiled with 10MB it give me this : > 0(0) convert_row(): No memory left > 0(0) convert_rows(): Error while converting row #62355 > 0(0) convert_result(): Error while converting rows > 0(0) store_result(): Error while converting result > 0(0) preload_udomain(): Error while doing db_query > 0(0) register_udomain(): Error while preloading domain 'aliases' > 0(0) release_connection(): Removing connection from the pool > 0(0) domain_fixup(): Error while registering domain > ERROR: error -1 while trying to fix configuration > 0(0) XLOG: destroy module ... > 0(0) DEBUG: tm_shutdown : start > 0(0) DEBUG: unlink_timer_lists : emptying DELETE list > 0(0) DEBUG: tm_shutdown : emptying hash table > 0(0) DEBUG: tm_shutdown : releasing timers > 0(0) DEBUG: tm_shutdown : removing semaphores > 0(0) DEBUG: tm_shutdown : destroying tmcb lists > 0(0) DEBUG: tm_shutdown : done > 0(20330) shm_mem_destroy > > thanks > > On 6/21/07, *Henning Westerholt* < henning.westerholt@1und1.de <mailto:henning.westerholt@1und1.de> > <mailto:henning.westerholt@1und1.de <mailto:henning.westerholt@1und1.de>>> wrote: > > On Mittwoch, 20. Juni 2007, Arun Kumar wrote: > > Hi > > > > 1. Is there any benefit of increasing the value > of PKG_MEM_POOL_SIZE and > > SHM_MEM_SIZE ? > > > > /*used only if PKG_MALLOC is defined*/ > > #define PKG_MEM_POOL_SIZE 1024*1024 > > > > /*used if SH_MEM is defined*/ > > #define SHM_MEM_SIZE 32 > > > > > > 2. I've compiled my ser with > > > > #define PKG_MEM_POOL_SIZE 1024*1024*512 > > Hello Arun, > > this is really to much private memory. You should not need more > then 10 MB, > even in quite large installations. Its much more reasonable to > increase the > shared memory parameter, e.g. to system memory / number of children. > > Cheers, > > Henning > > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > Users@openser.org <mailto:Users@openser.org> > http://openser.org/cgi-bin/mailman/listinfo/users >
On Donnerstag, 21. Juni 2007, you wrote:
hi
when I compiled with 10MB it give me this : 0(0) convert_row(): No memory left 0(0) convert_rows(): Error while converting row #62355 0(0) convert_result(): Error while converting rows 0(0) store_result(): Error while converting result 0(0) preload_udomain(): Error while doing db_query 0(0) register_udomain(): Error while preloading domain 'aliases'
This is an really old error, caused from preloading to much domain entries and such exhausting all the memory. Use a recent OpenSER version, and set a sane fetch_rows parameter.
http://www.openser.org/docs/modules/1.2.x/usrloc.html#AEN339
Cheers,
Henning
its a production machine so I can't upgrade to a newer version right now. Is there any thing that I can do to fix this problem
UsrLoc Stats Domain Registered Expired 'location' 325 2706 'aliases' 111841 0
removing user aliases from aliases tables can solve my problem ?
thanks
On 6/21/07, Henning Westerholt henning.westerholt@1und1.de wrote:
On Donnerstag, 21. Juni 2007, you wrote:
hi
when I compiled with 10MB it give me this : 0(0) convert_row(): No memory left 0(0) convert_rows(): Error while converting row #62355 0(0) convert_result(): Error while converting rows 0(0) store_result(): Error while converting result 0(0) preload_udomain(): Error while doing db_query 0(0) register_udomain(): Error while preloading domain 'aliases'
This is an really old error, caused from preloading to much domain entries and such exhausting all the memory. Use a recent OpenSER version, and set a sane fetch_rows parameter.
http://www.openser.org/docs/modules/1.2.x/usrloc.html#AEN339
Cheers,
Henning
Hello,
On 06/21/07 11:49, Henning Westerholt wrote:
On Mittwoch, 20. Juni 2007, Arun Kumar wrote:
Hi
- Is there any benefit of increasing the value of PKG_MEM_POOL_SIZE and
SHM_MEM_SIZE ?
/*used only if PKG_MALLOC is defined*/ #define PKG_MEM_POOL_SIZE 1024*1024
/*used if SH_MEM is defined*/ #define SHM_MEM_SIZE 32
- I've compiled my ser with
#define PKG_MEM_POOL_SIZE 1024*1024*512
Hello Arun,
this is really to much private memory. You should not need more then 10 MB, even in quite large installations. Its much more reasonable to increase the shared memory parameter, e.g. to system memory / number of children.
first we need to know what version of openser is running and how many location entries (and aliases if it is the case) are in place. Older versions used to load everything in private memory and then move to shared memory.
With openser 1.2.x, that problem is gone, as it is using db fetch mechanism. Also, the server is no longer blocked during loading, as it is done by first child, the rest can handle sip traffic immediately at startup.
Cheers, Daniel
Cheers,
Henning
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Arun Kumar -
Daniel-Constantin Mierla -
Henning Westerholt -
Morgan Gilroy