On Tue, 29 Jan 2013, Zeev Suraski wrote:

> From: Clint Priest [mailto:cpri...@zerocue.com]:
>
> > On 1/29/2013 5:23 AM, Anthony Ferrara wrote:
> >
> > > Additionally, I don't like the precedent that this sets for future 
> > > releases. That it's ok to break the timebox for some feature. In 
> > > this case I think we can justify it, but future cases may use this 
> > > to justify waiting when it's not completely justified in itself. 
> > > I'm not sure how we can rectify this concern, but I figured it was 
> > > worth mentioning.
> >
> > I would agree with this sentiment, time boxing from my own personal 
> > experience just completely breaks down if you let anything get in 
> > the way of it, if you let that box slip for any reason, other 
> > reasons become easily justifyable.  If 5.5 is due for release, we 
> > should not delay it for 2 months to get an opcode cache into core.
> >
> > Additionally:
> >
> > 1) I believe Optimizer+ is the opcode cache that's been discussed 
> > but it's not thread safe?
> 
> It's presently not thread safe.  Just to be sure we're all on the same
> page, this is only meaningful if you're running PHP on Windows and not
> using FastCGI;  It's completely meaningless in any other scenario (i.e.
> for the vast majority of users);  That said, adding thread safety support
> for Optimizer+ is a fairly easy task.  We've never done it because none of
> our commercial products use thread-safe PHP.  I'll update the RFC to
> clarify the scope of this limitation.

I wouldn't bother making it work with ZTS. If you want performance, you 
shouldn't be using it, and the other case I heard was "pthreads" in 
which case it plays no role,as all of the script is in memory anyway 
for the duration of the process.

cheers,
Derick

-- 
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug
Posted with an email client that doesn't mangle email: alpine

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to