Yesterday I somewhat reluctantly removed eAccelerator from my server (Debian Etch) and installed APC instead. Not because I wasn’t satisfied with performance of eAccelerator, but because the packaged version of it was not in the Debian repositories (Andrew McMillan provided the debs), and those debs weren’t upgraded at the same pace and thus broke my normal upgrade-routine. Moreover APC will apparently become a default part of PHP6 (making the Alternative PHP Cache the default opcode cache component). Installation was as easy as doing “pecl install apc” and adding apc to php.ini. Everything seems to be running as great as it did with eAccelerator (as most test seem to confirm).
Thanks for the tip, same problem here. I wasn’t able to install eaccelerator decently on Ubuntu either. So I replaced it with APC. Doesn’t look like the site is faster now, but maybe the throughput is just higher (since I have the impression the CPU load is now higher – maybe it is because the disk isn’t the bottleneck anymore).
I added this parameter to apc.ini:
apc.shm_size = 64
(see http://2bits.com/articles/high-php-execution-times-drupal-and-tuning-apc-includeonce-performance.html)
which makes it much faster now (apparently the default value assigns not enough memory for my site which results in a lot of swapping).
you can check the usage of APC’s shared memory with the apc_sma_info-function, which will (a.o.) return the amount of available memory. monitoring that value should help you to finetune the size of shared memory.
maar door al uw pets zit ik weeral op youtube eh man! must not click on related video’s, must not click on related video’s, … *click*