There actually is a fair amount of documentation, just most of it is in the source file. Take a look at:
zippy2/README zippy2/tclThreadAlloc.c Zippy2 allows you to override the Tcl threaded allocator functions, so you don't need to worry about recompiling Tcl with "USE_THREAD_ALLOC=0" in this case. To run, you'd do something like: env -i LD_PRELOAD=libhoard.so:libzippy.so TCL_ALLOC_DISABLE=1 bin/nsd -ft nsd.tcl The Zippy2 allocator is a complete work in progress, and has never been deployed in production. It might be better to look at the performance of threaded Tcl without the thread allocator (USE_THREAD_ALLOC=0) and hoard. Hope that helps! On 12/14/06, Agnieszka Kukałowicz <[EMAIL PROTECTED]> wrote:
For sure… Followed the instructions for Hoard for example, I ony set the LD_PRELOAD variable. And there is also no instructions for zippy2 to recompile TCL without DUSE_THREAD_ALLOC. So my question is if I want to use Hoard/Zippy2/Tcmalloc do I need to built TCL without the zippy memory allocator as you wrote? And the second thing… Maybe, It would be a good idea to put these instruction in README file in Zippy2 code? Agnieszka -----Original Message----- *From:* AOLserver Discussion [mailto:[EMAIL PROTECTED] *On Behalf Of *Nathan Folkman *Sent:* Wednesday, December 13, 2006 8:07 PM *To:* [email protected] *Subject:* Re: [AOLSERVER] tcmalloc Exactly right. Thanks for jogging my memory! ;-) Here's a snippet from one of our custom build scripts which might help: @echo "** MODIFYING TCL TO BUILD WITHOUT THE ZIPPY MEMORY ALLOCATOR **" cd $(ROOT_DIR)/tcl/unix && \ cat Makefile | sed -e 's/-DUSE_THREAD_ALLOC=1//' > Makefile.new && \ cat tclConfig.sh | sed -e 's/-DUSE_THREAD_ALLOC=1//' > tclConfig.sh.new && \ cp Makefile.new Makefile && \ cp tclConfig.sh.new tclConfig.sh On 12/13/06, *Jeff Rogers* <[EMAIL PROTECTED]> wrote: Nathan Folkman wrote: > What you need to do is build a version of Tcl that has support for threads, > but does not use the "Zippy" allocator. I seem to remember there being > issues with core Tcl that did not allow you to do this easily, but you'd > have to double check. Maybe try something like "--enable-threads > --disable-thread-alloc." If I recall from when I was poking at this, there is no configure flag to disable the threaded allocator; instead you need to edit the generated Makefile after you run "configure" and remove -DUSE_THREAD_ALLOC=1 from AC_FLAGS. And of course, 'make clean' before remaking or nothing will change. -J -- 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. -- Nathan Folkman [EMAIL PROTECTED] -- 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.
-- Nathan Folkman [EMAIL PROTECTED]
