UsrLoc Stats<br>Domain Registered Expired<br>'location' 325 2706<br>'aliases' 111841 0<br><br><span class="gmail_quote">On 6/21/07, <b class="gmail_sendername">Daniel-Constantin Mierla</b> <<a href="mailto:daniel@voice-system.ro">
daniel@voice-system.ro</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
Hello,<br><br>as said in the other email, I assume you are running an older version of<br>openser and have a lot of location (aliases) entries. I paste from the<br>other email:<br><br>Older versions used to load everything in private memory and then move
<br>to shared memory. With openser 1.2.x, that problem is gone, as it is<br>using db fetch mechanism. Also, the server is no longer blocked during<br>loading, as it is done by first child, the rest can handle sip traffic<br>
immediately at startup.<br><br>Just let me know the numbers in location/aliases to see a roughly<br>estimation of required memory. The best is to migrate to 1.2.1, which<br>solves this problem in a nice way, also is much faster in usrloc when
<br>dealing with large number of records.<br><br><a href="http://www.openser.org/docs/openser-performance-tests/#ul-tests">http://www.openser.org/docs/openser-performance-tests/#ul-tests</a><br><br>Cheers,<br>Daniel<br><br>
<br>On 06/21/07 12:00, Arun Kumar wrote:<br>><br>> hi<br>><br>> when I compiled with 10MB it give me this :<br>> 0(0) convert_row(): No memory left<br>> 0(0) convert_rows(): Error while converting row #62355
<br>> 0(0) convert_result(): Error while converting rows<br>> 0(0) store_result(): Error while converting result<br>> 0(0) preload_udomain(): Error while doing db_query<br>> 0(0) register_udomain(): Error while preloading domain 'aliases'
<br>> 0(0) release_connection(): Removing connection from the pool<br>> 0(0) domain_fixup(): Error while registering domain<br>> ERROR: error -1 while trying to fix configuration<br>> 0(0) XLOG: destroy module ...
<br>> 0(0) DEBUG: tm_shutdown : start<br>> 0(0) DEBUG: unlink_timer_lists : emptying DELETE list<br>> 0(0) DEBUG: tm_shutdown : emptying hash table<br>> 0(0) DEBUG: tm_shutdown : releasing timers<br>> 0(0) DEBUG: tm_shutdown : removing semaphores
<br>> 0(0) DEBUG: tm_shutdown : destroying tmcb lists<br>> 0(0) DEBUG: tm_shutdown : done<br>> 0(20330) shm_mem_destroy<br>><br>> thanks<br>><br>> On 6/21/07, *Henning Westerholt* <<a href="mailto:henning.westerholt@1und1.de">
henning.westerholt@1und1.de</a><br>> <mailto:<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>>> wrote:<br>><br>> On Mittwoch, 20. Juni 2007, Arun Kumar wrote:<br>> > Hi
<br>> ><br>> > 1. Is there any benefit of increasing the value<br>> of PKG_MEM_POOL_SIZE and<br>> > SHM_MEM_SIZE ?<br>> ><br>> > /*used only if PKG_MALLOC is defined*/
<br>> > #define PKG_MEM_POOL_SIZE 1024*1024<br>> ><br>> > /*used if SH_MEM is defined*/<br>> > #define SHM_MEM_SIZE 32<br>> ><br>> ><br>> > 2. I've compiled my ser with
<br>> ><br>> > #define PKG_MEM_POOL_SIZE 1024*1024*512<br>><br>> Hello Arun,<br>><br>> this is really to much private memory. You should not need more<br>> then 10 MB,<br>> even in quite large installations. Its much more reasonable to
<br>> increase the<br>> shared memory parameter, e.g. to system memory / number of children.<br>><br>> Cheers,<br>><br>> Henning<br>><br>><br>> ------------------------------------------------------------------------
<br>><br>> _______________________________________________<br>> Users mailing list<br>> <a href="mailto:Users@openser.org">Users@openser.org</a><br>> <a href="http://openser.org/cgi-bin/mailman/listinfo/users">
http://openser.org/cgi-bin/mailman/listinfo/users</a><br>><br></blockquote><br>