Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:210 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81739 invoked from network); 24 Mar 2003 14:07:01 -0000 Received: from unknown (HELO imf25bis.bellsouth.net) (205.152.58.199) by pb1.pair.com with SMTP; 24 Mar 2003 14:07:01 -0000 Received: from k4z4b4 ([67.33.185.215]) by imf25bis.bellsouth.net (InterMail vM.5.01.04.25 201-253-122-122-125-20020815) with SMTP id <20030324140905.SEWJ681.imf25bis.bellsouth.net@k4z4b4> for ; Mon, 24 Mar 2003 09:09:05 -0500 Message-ID: <004b01c2f20e$a787e440$4575fea9@k4z4b4> To: Date: Mon, 24 Mar 2003 09:07:07 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: re: ZTS performance From: cshmoove@bellsouth.net ("l0t3k") one observation i have is that in certain frequently called routines, TSRMLS_FETCH() is called rather than having the the thread environment passed in. zval_dtor comes immediately to mind (this only affects objects). the other thing that i wonder about is the current practice of macro access to fields of TLS globals, rather than a single fetch of a pointer to the global structure, then dereferencing from there. if you look at at zend_execute.c, you'll see what i mean. this is just an amateur's opinion, since i dont know the cost of macro call involved in such accesses. it just seems to me to be more efficient to incur the overhead once (whatever it is), and deref from there. l0t3k "Wojtek Meler" wrote in message news:20030324135821.E31290@wp-sa.pl... > Hi! > > Does anyone have any suggestions ? Maybe I should use different thread library ? > Maybe TSRM should be rewritten ? > Does anyone have any similar results (with code caching) ? > > regards, > Wojtek