Microbits » eaccelerator

More on eAccelerator

recon — Sun, 27 Dec 2009 22:27:04 +0000

Now that I’m correctly loading the extension (zend_extension_ts), eAccelerator is running smoothly.

I found something interesting in the event log yesterday:

PHP Warning:  [eAccelerator] This build of "eAccelerator" was compiled for PHP version 5.2.9. Rebuild it for your PHP version (5.2.9-2) or download precompiled binaries.

Now that error message makes perfect sense. The reason I didn’t see it the first time around is that PHP logged two messages separately at the same time. If I was reading a flat file log, I would’ve noticed it immediately.

Thread safety and PHP

recon — Sun, 27 Dec 2009 04:06:30 +0000

UPDATED

After a few seg-faults, I realized that eAccelerator isn’t thread safe (I was running it under a thread safe server)… It is thread safe… I just wasn’t loading it in thread safe mode (see the manual for details). Whoops.

eAccelerator

recon — Sun, 27 Dec 2009 00:59:46 +0000

After getting somewhat annoyed with the slowness of my blog, and having nothing better to do, I decided to setup eAccelerator. I’m pretty sure I tried setting it up a long time ago, but for some reason, didn’t finish.

Following the path of logic, I went to the eAccelerator website in search of the appropriate files. Their Windows section directed me to SiteBuddy, which had a nice collection of binaries for various PHP versions. After determining my PHP version (5.2.9-2), I tried the closest match (5.2.9), and was greeted by the following error in the Windows event log:

Unable to start eAccelerator module in Unknown on line 0.

My initial reaction to the error: what the ****… (UPDATE: See this post for more details) After a quick Google search, I found that PHP modules must be built for the EXACT PHP version you plan to use them on.

Since I have just about every Microsoft C++ compiler, I figured compiling a new eAccellerator module for my version of PHP would be simple. I downloaded the archived PHP files I needed (now I understand why they keep archives), switched to the release configuration, and pressed build.

error C2466: cannot allocate an array of constant size 0

My reaction to this was about the same as the other one. After half an hour, I tracked down and fixed the problem, which was a broken Windows build configuration (which the PHP developers KNEW about, and marked as “Wont Fix”).

The solution was to make the changes suggested by sailormax.

In the end, everything compiled, and you’re reading my post through eAccelerator. I noticed that blog page loads are 2 – 3 times faster.