On Jan 24, 2005, at 8:55 PM, Nathan Folkman wrote:
Below is a quick and dirty page you can use to print out some info from the "Zippy" memory allocator. Not pretty, but might help you gain some insight into what is going on. Pay close attention to the total stats at the end of the page. By design the memory allocator is somewhat of a memory hog (note the high overhead), however, you'll notice the lock contention is nearly non-existent. In practice memory is "cheap" and lock contention is to be avoided at all costs! Hope this helps!
Thanks, Nathan!
I've run this, but I'm not sure how to interpret the output. The full page is at
http://www.furfly.net/janine/memory-pools.html
The total stats you mentioned are:
Bytes Requested: 17754181 Bytes Free: 1980544 Bytes Allocated: 28301396 Bytes Wasted: 10547215 Byte Overhead: 59.41% Mutex Locks: 10660 Mutex Lock Waits: 0 Lock Wait Ratio: 0.00% Gets/Puts: 1722429 Lock Avoidance: 99.38%
The Bytes Wasted seems pretty high, but without knowing why or how they are considered wasted it's hard to know what to think about that. Does this suggest anything to you?
It seems like it would be useful to be able to look at Tcl's data structures and see how much memory is allocated to NSVs, etc, but I don't know how to do that, if it's even possible.
thanks,
janine
-- 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.
