Cold Feet wrote:
hi all,
for the first month of being up on kannel 1.1.6 development release it has its ups
and downs on its live run. on its first week several times it went down by itself...
and so i recompiled it with additional flags and now have remained up and running and
i can say
Oded Arbel wrote:
I'm not sure how native malloc works, but the checking malloc (which we use
always) has an upper limit on the number of allocations allowed. if you want to use
more memory you will have to recompile.
and this information should *definitly* go into our FAQ file as first
Harrie Hazewinkel kirjoittaa perjantaina, 31. toukokuuta 2002, kello
12:36:
--On Friday, May 31, 2002 9:57 AM +0200 Stipe Tolj tolj@wapme-
systems.de wrote:
yep, that may be. Aarno, what do you mean of this? Did you recognize
anything at your benchmark testings?
I understood the others
Message-
From: Cold Feet [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 4:16 AM
To: [EMAIL PROTECTED]
Subject: RE: version 1.1.6 processing limits
hi again,
does it help and give better result if i upgrade the memory
to say 1GB from its present 256MB configuration? since
Arbel [EMAIL PROTECTED]
Date: Thu, 30 May 2002 10:14:20 +0300
To: Cold Feet [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: RE: version 1.1.6 processing limits
I'm not sure how native malloc works, but the checking malloc (which we use
always) has an upper limit on the number of allocations
-Original Message-
From: Cold Feet [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 12:41 PM
To: [EMAIL PROTECTED]
Subject: RE: version 1.1.6 processing limits
hi oded,
what do you mean by recompile
if i have recompiled it on a 256MB memory before
and this time i
if you want to use the native malloc, then configure it with
malloc=native. I don't know what the memory limit is in native
malloc, but I assume there are none. if you are using a checking
malloc, and want to use a bigger memory pool then you'll have to
change the malloc code in
--On Thursday, May 30, 2002 10:14 AM +0300 Oded Arbel [EMAIL PROTECTED]
wrote:
I'm not sure how native malloc works, but the checking malloc (which we
use always) has an upper limit on the number of allocations allowed. if
you want to use more memory you will have to recompile.
Just a
thanks oded... this should give me a start on what to do
- Original Message -
From: Oded Arbel [EMAIL PROTECTED]
Date: Thu, 30 May 2002 16:06:20 +0300
To: Cold Feet [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: RE: version 1.1.6 processing limits
if you want to use the native
From: Harrie Hazewinkel [EMAIL PROTECTED]
--On Thursday, May 30, 2002 10:14 AM +0300 Oded Arbel [EMAIL PROTECTED]
Just a thought, but is the amount of system-call casuing some problems.
Not knowing how much there are, but malloc is one of them.
If so, maybe some memory handling needs to be
... correct me if i am wrong... anyhow, this is
just my thoughts...
- Original Message -
From: Oded Arbel [EMAIL PROTECTED]
Date: Wed, 29 May 2002 11:03:09 +0300
To: Cold Feet [EMAIL PROTECTED]
Subject: RE: version 1.1.6 processing limits
This question should be asked on the users list
hi all,
for the first month of being up on kannel 1.1.6 development release it has its ups and
downs on its live run. on its first week several times it went down by itself... and
so i recompiled it with additional flags and now have remained up and running and i
can say i am to the point
12 matches
Mail list logo
