Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:234 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85733 invoked from network); 24 Mar 2003 21:20:57 -0000 Received: from unknown (HELO mail.wp-sa.pl) (212.77.102.105) by pb1.pair.com with SMTP; 24 Mar 2003 21:20:57 -0000 Received: from wp-sa.pl (mail.wp-sa.pl [212.77.102.105]) by mail.wp-sa.pl (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0HC900ACHVAJ3K@mail.wp-sa.pl> for internals@lists.php.net; Mon, 24 Mar 2003 22:20:43 +0100 (CET) Received: from [62.181.161.66] by mail.wp-sa.pl (mshttpd); Mon, 24 Mar 2003 22:20:43 +0100 Date: Mon, 24 Mar 2003 22:20:43 +0100 To: zeev@zend.com Cc: internals@lists.php.net Message-ID: <3b6af3b7d2.3b7d23b6af@wp-sa.pl> MIME-version: 1.0 X-Mailer: iPlanet Webmail Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en Subject: Re: [PHP-DEV] ZTS performance From: wmeler@wp-sa.pl > ZTS is *always* going to be slower than non ZTS. Yes, but it can be faster than it is. PHP doesn't use almost any shared resources (compiled regexs?) so why it is so slow ? Thread-safe syscalls ? I don't think so. > There's no need for rewriting TSRM, it's roughly as fast as it can be. Things changes ... Now we have AD2003 and __thread keyword in gcc. I suppose that if we use it we could get rid of all this TSRMLS*. I know - PHP is not for linux only - but we could have it in TSRM implementation. I'm sure that compiler will optimize it better if __thread keyword will be used instead of TSRMLS*. Regards, Wojtek