[sr-dev] SER crash : Segmentation fault

[inge]

Hello Andrei, Henning,

So we will up the PKG_MEM_POOL_SIZE to 4MB.

Andrei : we have update to the lastest CVS snapshot ser-0.9.9
+cvs20090925. Is that correct for avoid the lastest problem ?

Thanks for your detailed answers !

Regards,

Adrien.

Le lundi 28 septembre 2009 à 20:24 +0200, Andrei Pelinescu-Onciul a
écrit :
> On Sep 28, 2009 at 18:53, inge <inge at legos.fr> wrote:
> > Hi Henning,
> > 
> > 40MB x Number of child ? isn't it ?
> 
> It doesn't use 40 MB x number of process physical memory.
> In your case it will use as much as needed to temporary load the
> location table on startup, but only in _one_ process. The rest of the
> processes will use < 1Mb, so the total physical memory used will be
> something like no_of_processes-1 + size_needed_for_location.
> Think of  the PKG_MEM_POOL_SIZE like an upper bound and not actually
> used memory. You need to worry about PKG_MEM_POOL_SIZE only if you have
> memory overcommit disabled (and even in that case only if you exceed the 
>  physical memory configured on the box).
> 
> The reason for the low 1Mb default in 0.9.x (and 4Mb in newer versions)
> is debugging. Most people don't need more then 1Mb and memory leaks are
> caught much earlier this way.
> I'll increase the default for 0.9.9.
> 
> > 
> > So the parameter can be set to "40 x 1024 x 1024" ?
> > 
> > The database contains something than 4500 users. The server runs with
> > 4GB of memory. How many users do you have on your server ?
> 
> Andrei