On Sun, April 1, 2012 7:19 am, Florian Anderiasch wrote:
> I'd appreciate any hints on how to tackle this serious concern.
If this actually wasn't an April Fool's joke...
Never ignore the user contributed notes after doing a search like:
http://php.net/roman
http://us3.php.net/manual/en/functio
On 05/24/2012 08:23 AM, Tom Boutell wrote:
> I've seen this statement before about the impact of caching the actual
> compilation (or mere tokenization?) to bytecode being very small
> compared to the impact of avoiding disk access. I am curious if there
> are any measurements breaking this down. R
(I'm not questioning that APC makes an enormous difference. That's
painfully obvious from 100 miles away on our servers (: )
On Thu, May 24, 2012 at 11:23 AM, Tom Boutell wrote:
> I've seen this statement before about the impact of caching the actual
> compilation (or mere tokenization?) to bytec
I've seen this statement before about the impact of caching the actual
compilation (or mere tokenization?) to bytecode being very small
compared to the impact of avoiding disk access. I am curious if there
are any measurements breaking this down. Read-only access to code in
files already buffered b
