John Buckman wrote:
On Fri, Feb 29, 2008 at 05:41:44PM +0100, Juan Jos? del R?o [Simple
Option] wrote:
In my case I run AOLServer with customized code on top of it. No
OpenACS. No modules except nspostgres. In 32 bits it works like a charm.
No memory leaks. It simply works (damn fast!).
Hm, so you see memory leaks when compiled for 64 bit, but none when
compiling the same code 32 bit - interesting. Can you reproduce the
leakage under Valgrind?
FYI, I see no leaks under 64bit, but I do see a fair amount of "bloat".
On 32bit Linux, my nsd process ran around 1.2gb, while under 64bits I'm
around 7gb.
However, no leaks.
After a few days my nsd process size does not continue to grow, it is
stable at ~17gb (I have a 10gb BerkeleyDB cache in process).
I'm not clear on why anyone would need 64bit Aolserver unless they
needed to use more than 2gb of RAM.
I'm also not clear that the bloat is aolserver, and not tcl or other
libraries I'm using.
Move from 1.2gb to 7gb stable running state by just shifting from 32-bit
build to 64-bit build sounds a little fishy to me. I would expect, at
most, a 2x increase in process size (given theoretical changes).
However, theory and practice ... it could be that the alignment of data
in Tcl and/or AOLServer for 64-bit processes is just very poor, causing
massive overallocation.
Jeff
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
