On Feb 29, 2008, at 6:03 PM, Tom Jackson wrote:
I've done load testing with 64bit, watching the memory footprint as
I go,
never grew for me with 100k/test.
It could be that the 64bit uses more memory, and you just never
noticed that
your application grew in memory footprint over time and then
stablized. The
best way to test it is to do load tests for particular packages and
watch
memory, it shouldn't take long to see if it keeps growing while
hitting a
single page. But multiple pages, which simulates real world loads will
usually grow.
I do that. I've run 100 simultaneous copies of wget in its "crawl"
mode (where it follows links) and after 24h I had no process growth.
I suspect that my bloat is actually a tcl thread holding a large data
structure in memory, and then when it exits, the OS keeping hold of
that memory in that thread to avoid semaphore locking if the memory
went back to the general pool. I've seen that behavior on Linux and
Windows.
So, lots of Tcl threads, all having run at some large memory
footprint size at some time, that would cause bloat.
-john
$ uname -a
Linux localhost 2.6.18-gentoo-r4 #1 SMP Mon Nov 20 16:49:16 UTC
2006 x86_64
AMD Turion(tm) 64 X2 Mobile Technology TL-52 AuthenticAMD GNU/Linux
tom jackson
On Friday 29 February 2008 09:34, John Buckman wrote:
I my case... My only desire would be getting AOLServer to work
perfectly
on 64bit platforms.
I have not heard of anyone that has AOLServer working on it with a
decent load (more than 10K hits / day) on a 64 bits platform and do
not
restart it for at least 1 month.
Aolserver/64bits works perfectly for me at BookMooch.com, I run it
entirely on a single 8 core server with 24bg of RAM, running debian.
I'm doing a bit less than a half-million hits a day, and every one of
those hits is a dynamically created tcl page, with database
operations (my images are served from a separate, dumb http server)
There are some minor compilation issues on 64 bit, that would take
1/2 a day to permanently solve in the cvs tree (Dossy helped me
compile mine, in my case) but otherwise it's 100% stable.
My uptime is about 2 months. I sometimes have to reboot due to a
semaphore deadlock, but I think that's in the database library, not
aolserver (it happens during my nightly full backup).
-john
www64:~# uname -a
Linux www64 2.6.18-5-amd64 #1 SMP Thu Aug 30 01:14:54 UTC 2007 x86_64
GNU/Linux
www64:/usr/local/aolserver/servers/bookmooch/modules/nslog# wc -l
access.log.001
432861 access.log.001
--
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.
--
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.
--
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.
