Re: Re: WinCache 1.3.5 release on SourceForge
| From: | Jan Ehrhardt | Date: | Fri, 23 Aug 2013 13:41:19 +0000 |
| Subject: | Re: Re: WinCache 1.3.5 release on SourceForge | ||
| References: | 1 2 3 4 5 6 | Groups: | php.windows |
| Request: | Send a blank email to php-windows+get-31156@lists.php.net to get a copy of this message | ||
Pierre Joye in php.windows (Fri, 23 Aug 2013 09:01:55 +0200):
>In the long run yes, or maybe. Right now the last release is totally
>unusable. For various reasons, some fixable and other will be hardly
>fixable without changes in the engine.
I know there are some issues:
https://github.com/zendtech/ZendOptimizerPlus/issues?state=open
And OPcache for Windows is not behaving properly, because it uses fixed
memory addresses for the cache (although the X64 version is not using
the hard-coded address).
I would not be surprised if a report like this is caused by the bad
memory allocation of OPcache:
http://www.apachelounge.com/viewtopic.php?p=25439#25439
But I would not call it "totally unusable". It is running fine on my
Win2k8 production server (still PHP 5.3) and on my Win2k8 development
server (PHP 5.3 as mod_php alongside PHP 5.5 x64 mod_fcgid).
I am running Apache 2.4.6, Keith is running IIS. What makes you say it
is unusable?
Jan