From 662b5db35fc8847ebc31b657a351e13144bf0815 Mon Sep 17 00:00:00 2001 From: Matthias Glaub Date: Sun, 9 Nov 2014 02:09:51 +0100 Subject: [PATCH] typos --- _posts/14-02-01-Opcode-Cache.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/14-02-01-Opcode-Cache.md b/_posts/14-02-01-Opcode-Cache.md index bac78dc..6a93de5 100644 --- a/_posts/14-02-01-Opcode-Cache.md +++ b/_posts/14-02-01-Opcode-Cache.md @@ -6,10 +6,10 @@ anchor: opcode_cache ## Opcode Cache {#opcode_cache_title} When a PHP file is executed, under the hood it is first compiled to opcodes and, only then, the opcodes are executed. -If a PHP file is not modified, the opcode will always be the same. This means that the compilation step is a waste of CPU resources. +If a PHP file is not modified, the opcodes will always be the same. This means that the compilation step is a waste of CPU resources. This is where opcode caches come in. They prevent redundant compilation by storing opcodes in memory and reusing it on successive calls. -Setting up an opcode cache is a matter of minutes, and your application will speed up significantly. There's really no reason not to use it. +Setting up an opcode cache takes a matter of minutes, and your application will speed up significantly. There's really no reason not to use it. As of PHP 5.5, there is a built-in opcode cache called [OPcache][opcache-book]. It is also available for earlier versions.