Php Accelerators
APC binaries for PHP 4.x (windows builds)
Submitted by chris on September 7, 2006 - 02:22. Php Accelerators | Downloads | PHP FeaturedUpdated: APC download using latest code (3.0.11).
Please find following the compiled binaries of APC for Windows
using Microsoft VC++ 6. For
PHP 5 versions (following link should be updated soon):
PHP APC binaries for PHP 5.x.
If you need a version not offered here, let us know (post comment).
APC binaries for PHP 5.x (windows builds)
Submitted by chris on September 7, 2006 - 00:55. Php Accelerators | Downloads | PHP FeaturedUpdated: APC download using latest code (3.0.12p2).
eAccelerator
Submitted by chris on January 15, 2006 - 17:29. Php Accelerators | PHP FeaturedWe have been using this PHP accelerator (0.9.X), on multiple servers, for a long time. It's used on some high traffic sites without any problem.
Install:
a) Download a copy of eAccelerator that is compatible with your version
of PHP.
This can be an issue with eAccelerator. Sometimes it can take a
little time before the Windows binaries are available for the most recent version of PHP.
Older eAccelerator Releases
Submitted by chris on May 5, 2008 - 19:33. Php Accelerators | DownloadsOlder versions of eAccelerator.
For more current version of eAccelerator for PHP4 or eAccelerator for PHP5
Running Apache + PHP + Accelerators under Windows 2003
Submitted by chris on September 19, 2006 - 20:54. Apache Install | Php Accelerators | Apache Bugs or Errors | PHP Bugs or Errors | PHP InstallI have been getting some instability running Apache with PHP + Accelerators under Windows 2003. I will log my finds in this article. Visit regularly for updates. I ended up running 7 Apaches on a Windows 2003 Server to test all different kinds of configurations. Recently because it was becoming complex, I started logging my finds. This page is probably for the hardcore debugging type...
Mitigating factors:
- Most crash seem to happen because of load (with very low traffic you might
never experience problems).
- My PHP applications are very demanding. Especially Gallery2 which relies on
external libraries for processing images. Again other PHP applications might not
experience these problems.
-If you have issues with IIS, these finding might also be applicable.
Xcache a new PHP accelerator ? (updated version 1.0.2)
Submitted by chris on August 16, 2006 - 11:43. Php Accelerators | PHP FeaturedIt looks like the author of Xcache grew frustrated with the current offering of PHP accelerators and decided to build a simple stable PHP accelerator. For example, eAccelerator works perfectly on multiple servers here but on others it crashes multiple times a day. I'm still investigating this: eAccelerator crash
eAccelerator crash
Submitted by chris on August 16, 2006 - 09:32. Php Accelerators | PHP Bugs or Errors | PHP FeaturedeAccelerator crash (Updated)
I've created an article to try to track what works and what doesn't: Running Apache + PHP + Accelerators under Windows 2003
After moving a site with some traffic to an Apache 2.2.x server, I have been getting multiple Apache crash per day. Before I was only getting these about once a week. Here is what the error looks like in the Apache error.log:
eAccelerator binaries for PHP 4.x (windows builds)
Submitted by chris on August 4, 2006 - 17:10. Php Accelerators | DownloadsPlease find following the compiled binaries of eAccelerator for Windows
APC problem with Gallery 2
Submitted by chris on May 22, 2006 - 22:16. Php Accelerators | Drupal Modules | PHP Bugs or ErrorsUnder Apache 2.2.2 and 2.0.55 using APC (3.0.11-dev) I could not delete an image using Gallery2.
My temporary solution is to disable caching of Gallery2 classes in APC with:
apc.filters="-g2.*\.class"
eAccelerator problem with PHP: Crash under Apache
Submitted by chris on May 22, 2006 - 22:06. Php Accelerators | Drupal Modules | PHP Bugs or ErrorsOnce in a while under Apache 2.0.55 or 2.2.2, I
would get a crash with a line like the following in the log:
[7508] EACCELERATOR: PHP crashed on opline 48 of preg_replace() at
G:\DomZeus\sitebuddycom\wwwroot\modules\search.module:354
This mostly likely an eAccelerator bug (not 100% sure).
Meanwhile here is a solution to try to avoid it. Since in my case the error
happens regularly (once a day?) with the file search.module, I decided to tell
eAccelerator to stop trying to cache that file with:

