hi, On Wed, Jan 30, 2013 at 7:42 AM, Stas Malyshev <smalys...@sugarcrm.com> wrote: > 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
" I can confirm the ICU version 3.8 worked well" Every maintained software (with active users ;) has bugs, which get fixed. > 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. Yes, but they are very open to get these issues fixed. >> 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. We do only do share nothing for the engine (related to script execution). There are other parts where we do share (realpath for one, pcre, etc.). Also I think that's something we should investigate instead of taking (yet again) the easiest or trendy way. >> 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. It is not unicode per se and there is not necessary a conversion happening, at least with NTFS filesystems. But that's another topic :) >> 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. But you ignore that TLS brings ZTS in line with NTS from a performance point of view. And it is only one of the possible gain. >> 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. I'd to disagree. And giving up only because it may require some more work sounds really bad to me. > >> 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? Nice to totally ignore the results you were asking for... And as of why, these changes could not be done in 5.x. We discussed the idea with the engine guys back then, and even last year again. Anyway, I have given enough arguments and this discussion is being in a loop now. Cheers, -- Pierre @pierrejoye -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
