[OpenSER-Users] Re: [Users] regarding memory usage

[Arun Kumar]

UsrLoc Stats
Domain Registered Expired
'location' 325 2706
'aliases' 111841 0

On 6/21/07, Daniel-Constantin Mierla <daniel at 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 at 1und1.de
> > <mailto:henning.westerholt at 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 at openser.org
> > http://openser.org/cgi-bin/mailman/listinfo/users
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kamailio.org/pipermail/users/attachments/20070621/13787ac3/attachment.htm