Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65473 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29962 invoked from network); 30 Jan 2013 06:42:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Jan 2013 06:42:28 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.163 smtp163.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.163] ([67.192.241.163:47983] helo=smtp163.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C2/E3-09318-3D0C8015 for ; Wed, 30 Jan 2013 01:42:27 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp16.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 0FA6E405AA; Wed, 30 Jan 2013 01:42:25 -0500 (EST) X-Virus-Scanned: OK Received: by smtp16.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 8B892405B2; Wed, 30 Jan 2013 01:42:24 -0500 (EST) Message-ID: <5108C0CF.6000206@sugarcrm.com> Date: Tue, 29 Jan 2013 22:42:23 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Pierre Joye CC: Zeev Suraski , PHP internals References: <51086022.2060607@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] ZTS - why are you using it? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I did not check latest ICU code base but we never had any issues in > intl in ZTS. However you are right, since 5.3.0 most TS issues were in One of them has to do with number formatting, so if you have a number of apps that use different locale settings on the same server, which have different number separators, you may encounter it. Not a frequent use case, though. See: http://bugs.icu-project.org/trac/ticket/6711 Not unique to TS, but there might be ones that are, if they use globals in this manner. Just showing that modern libraries are still having this kind of issues, and it's very hard to get maintainers to fix them. > I never said fcgi performs badly. What I say is that Windows design is > not process based, none of the hiperformence tools available on this > platform is based on threads (AD, IIS, asp.net, etc.). ITYM based or processes, or s/none/all/. But so what? For IIS case threads are fine, but for our case - shared-nothing - they don't help us much. No idea what asp.net does but they probably designed it to be threaded from scratch, so it probably has very different architecture than PHP. > Filesystem is getting better, it is already better in 5.3.0+ and will > be a bit better in 5.5.0 (if I got the time to do it :/). We do not > use the unicode API yet (for IO or FS), so no real impact yet but a > few functions that still have to use it in some libs or in core. AFAIR all APIs that go into filesystem, C library, etc. ultimately end up with Unicode - i.e. > To bring zts in line with NTS in term of performance is possible, look > at Arnaud's 1st draft for a TLS support in php: > > https://wiki.php.net/rfc/tls TLS is nice, I have nothing against TLS, and if somebody wants to get behind the effort to get ZTS to use TLS, great. But I was talking about cost of setting up envt for PHP script, which is not going to change. You need to initialize all the globals, create all the structures, etc. etc. - it's all not free. > The IIS pipeline architecture allows much more than only auth, much more. I know, it's just an example. I'm just saying PHP request init is expensive, and I'm not even sure we can do proper init on early stages of IIS request... So PHP may not be the best thing to use inside IIS pipeline in general case. > ease the developer work and reduce the wtf factors. TLS is one of > them. Fine, so who's going to do this? This RFC is marked with 2008, now it's 2013 and it didn't happen. Why? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227