The key, it seems to me, is that the memory footprint stablizes over time in a real world situation. A memory leak is best proven by watching memory grow while visiting a limited set of pages, essentially a stable load. Visiting a single page (with the same result) over and over should not cause any growth over time if there are no leaks in the code being executed.
tom jackson On Friday 29 February 2008 10:57, Jeff Hobbs wrote: > 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. -- 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.
