Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40075
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.134.189 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=from:to:subject:date:user-agent:mime-version:content-type
         :content-transfer-encoding:content-disposition:message-id;
        b=Uxjz8Iyk3gCB6cOC5d9Wa6vHOI/8J6VBmKR3FtcHZYC6rGEZa7Bz9HS6bVjSpV/EXJ
         VKITF4DqTv/okFgwYNHFRbKMQJWPN2BaJ0H4WOKMwzbOMUnMZTtiRijYKZpbZMJ3A3U5
         YTFynuvgw6o1UrDvayQ4YVVHricWg/anGBbh4=
To: internals@lists.php.net
Date: Sun, 24 Aug 2008 18:37:09 +0200
User-Agent: KMail/1.10.0 (Linux/2.6.26-noch; KDE/4.1.0; i686; ; )
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-ID: <200808241837.10208.arnaud.lb@gmail.com>
Subject: [RFC] Native TLS for globals in ZTS
From: arnaud.lb@gmail.com (Arnaud Le Blanc)

Hi,

I have written a RFC about my patch at http://wiki.php.net/rfc/tls

The goal of this patch is to reduce the performance overhead of ZTS builds.

Since the initial patch I made more research on various implementations of 
TLS: Linux, FreeBSD, Solaris, Windows. Based on what I found I wrote a new 
patch to avoid the problems of the initial one and the results on bench.php 
are as follows:


non-ZTS 
                         3.7s


ZTS unpatched 
                   5.2s


ZTS-patched, native TLS disabled 
5.0s


ZTS-patched, native TLS enabled 
 4.2s


Regards,

Arnaud