"Rasmus Lerdorf" wrote:
> shire wrote:
>> I agree for the general case, in our development environment though this
>> might cause some pains. But we could always start there and see how it
>> goes. I agree that Xdebug isn't really a use case we always need to
>> optimize for.
>
> Is it ever a ca
shire wrote:
> I agree for the general case, in our development environment though this
> might cause some pains. But we could always start there and see how it
> goes. I agree that Xdebug isn't really a use case we always need to
> optimize for.
Is it ever a case we need to optimize for? If y
Rasmus Lerdorf wrote:
shire wrote:
I agree for the general case, in our development environment though this
might cause some pains. But we could always start there and see how it
goes. I agree that Xdebug isn't really a use case we always need to
optimize for.
Is it ever a case we need to o
Rasmus Lerdorf wrote:
Gopal V wrote:
shire wrote:
http://tekrat.com/downloads/bits/apc_lazy_php53.patch
You should be able to apply the above patch to the latest PHP_5_3
branch, and recompile the latest APC CVS against it. Two ini settings
enable/display lazy loading:
apc.lazy_functions=On/
Gopal V wrote:
> shire wrote:
>
>> http://tekrat.com/downloads/bits/apc_lazy_php53.patch
>>
>> You should be able to apply the above patch to the latest PHP_5_3
>> branch, and recompile the latest APC CVS against it. Two ini settings
>> enable/display lazy loading:
>>
>> apc.lazy_functions=On/Off
shire wrote:
http://tekrat.com/downloads/bits/apc_lazy_php53.patch
You should be able to apply the above patch to the latest PHP_5_3
branch, and recompile the latest APC CVS against it. Two ini settings
enable/display lazy loading:
apc.lazy_functions=On/Off
apc.lazy_classes=On/OFf
Awesom
