note 89979 added to function.apc-compile-file
| From: | Glen at osu1 dot php dot net | Date: | Tue, 31 Mar 2009 22:44:05 +0000 |
| Subject: | note 89979 added to function.apc-compile-file | ||
| Groups: | php.notes | ||
| Request: | Send a blank email to php-notes+get-152668@lists.php.net to get a copy of this message | ||
There are reasons to use this routine. I can think of two:
- a busy website will have multiple web servers, and before one is brought online (via load
balancer), the cache is built. This prevents problems of having too many cache misses in a short
period on your entire code base, which could be massive, and cause problems.
- a website where the apc.stat flag is set to zero. That setting provides significant performance
savings because no 'stat' needs to be performed on PHP code files. But they are not
automatically rebuilt when changed. So what do you do when your code changes? Restart Apache, or
manually clearing the APC cache with apc_clear_cache() - but both will clear the entire cache.
There may be cases where it is much better to recompile select files instead. Some sites store data
(that rarely changes) in PHP code to make good use of the opcode cache, updating that file and
selectively compiling it would make writes efficient too.
----
Server IP: 208.69.120.35
Probable Submitter: 71.132.141.164
----
Manual Page -- http://www.php.net/manual/en/function.apc-compile-file.php
Edit -- https://master.php.net/note/edit/89979
Del: integrated -- https://master.php.net/note/delete/89979/integrated
Del: useless -- https://master.php.net/note/delete/89979/useless
Del: bad code -- https://master.php.net/note/delete/89979/bad+code
Del: spam -- https://master.php.net/note/delete/89979/spam
Del: non-english -- https://master.php.net/note/delete/89979/non-english
Del: in docs -- https://master.php.net/note/delete/89979/in+docs
Del: other reasons-- https://master.php.net/note/delete/89979
Reject -- https://master.php.net/note/reject/89979
Search -- https://master.php.net/manage/user-notes.php