From dd4c0f992f1ac252c1ab493b394704a2dc484fe8 Mon Sep 17 00:00:00 2001 From: Igor Radovanov Date: Sun, 31 Jul 2022 16:26:39 +0200 Subject: [PATCH] Fix broken link - Zend Engine 2 Opcodes --- _posts/14-02-01-Opcode-Cache.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/14-02-01-Opcode-Cache.md b/_posts/14-02-01-Opcode-Cache.md index fe63ed3..3a0fcc4 100644 --- a/_posts/14-02-01-Opcode-Cache.md +++ b/_posts/14-02-01-Opcode-Cache.md @@ -5,7 +5,7 @@ anchor: opcode_cache ## Opcode Cache {#opcode_cache_title} -When a PHP file is executed, it must first be compiled into [opcodes](https://secure.php.net/manual/internals2.opcodes.php) (machine language instructions for the CPU). If the source code is unchanged, the opcodes will be the same, so this compilation step becomes a waste of CPU resources. +When a PHP file is executed, it must first be compiled into [opcodes](https://php-legacy-docs.zend.com/manual/php4/en/internals2.opcodes) (machine language instructions for the CPU). If the source code is unchanged, the opcodes will be the same, so this compilation step becomes a waste of CPU resources. An opcode cache prevents redundant compilation by storing opcodes in memory and reusing them on successive calls. It will typically check signature or modification time of the file first, in case there have been any changes.