| | 1 | = PHP Optimizing software (APC = |
| | 2 | |
| | 3 | May First/People Link is currently (2008-12-17) experimenting with [http://us2.php.net/apc the Alternative PHP Cache] PHP optimizer. |
| | 4 | |
| | 5 | If successful, APC will be enabled on all shared servers. |
| | 6 | |
| | 7 | Normally, everytime a user requests a PHP file on a web server, the server has to "compile" the php script - which means translate it into code that the processor can execute. This compilation process can be CPU intensive on busy machines. APC stores compiled PHP files in memory and re-serves the compiled files rather than re-compiling them for every request. This approach saves a lot of CPU time, making the scripts run faster. |
| | 8 | |
| | 9 | There are two good articles on the success of APC with Drupal sites: [http://blogs.activestate.com/jeffg/2007/03/apc_and_drupal_.html One by Jeffg] and another [http://2bits.com/articles/benchmarking-drupal-with-php-op-code-caches-apc-eaccelerator-and-xcache-compared.html on 2bits]. |
| | 10 | |
| | 11 | In addition, I've found a [http://realize.be/odd-and-evil-things couple] [http://drupal.org/node/48946 references] to segfaults caused by APC and PHP, which we should be wary of. |
