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