25 Jun
2004
25 Jun
'04
12:26 a.m.
Thanks Andrei :-)
- Atle
* Andrei Pelinescu-Onciul <pelinescu-onciul(a)fokus.fraunhofer.de> [040624 14:14]:
On Jun 24, 2004 at 12:54, Andreas Granig
<a.granig(a)inode.at> wrote:
Andrei Pelinescu-Onciul wrote:
[...]
On Jun 21, 2004 at 19:47, Atle Samuelsen
<clona(a)cyberhouse.no> wrote:
D'oh, same problem again here now (Ser 0.8.12)!
It started with log entries like this:
Some more update.. got the same problem today..
and when it happend, ser
blocked. and I got ALOT of these error messages. Anybody know why ?
Ser runs out of "local" memory. The localtions are first loaded in local
(per process memory) and copied and inserted in the usrloc shared memory
list. (probably you have a lot of entries)
By default ser uses maximum 1Mb of local memory/process. Try to
increases it to a bigger value.
Change PKG_MEM_POOL_SIZE in config.h and recompile.
After deleting 100 entries from location it came up again. Hope that the
increase of PKG_MEM_POOL_SIZE to 2MB helps.
You'll be ok until you reach twice the location table size you have
right now.
So it seems that after about 6300 entries or so in location Ser stops
working with the default configuration!? I'd be interested in how many
users do other Ser-Servers out there serve? Are there similiar problems?
Yes there are and you are right they usually start at ~6000 entries.
We will either increase the default temp. memory size or we will switch
to shared memory for loading the locations tables on startup. The ideea
behind the local memory is to have some kind of private per process,
very fast to allocate memory space, used mainly for temporary stuff.
However in the usrloc case since the tables are loaded on startup we
don't care so much about the performance and we could switch to shared
memory (which is by default 32Mb and can be changed with the command
line switch -m).
Andrei