apc

we are using php5.4, apc 3.1.13 with apache2 and mod_php and have every now and then the problem that apc opcode cache seems to forget cached data after a apache reload (for example after a logrotate). This results sometimes in fatal errors with "Call to undefined method". We do not change the files in any way before the error occurs, and after an apache restart the problem is gone. When we release a new version of our code, we have the next and the current version of our application in the filesystem and switch them via unlink the current and symlink the new version. I think this way apc adds

I have two sites using the Symfony2 framework that have similar files. The sites are both on the same server and use APC cache. I have noticed that some items that are on one site are then used on another site. Any APC that has been used have different and unique keys. Is there some way of splitting the APC cache for each site or set a prefix or something? Have you tried to use ApcUniversalClassLoader() ? According to manual , in your autoload.php you can boot APC with different keys: require __DIR__.'/../vendor/symfony/src/Symfony/Component/ClassLoader/ApcUniversalClassLoader.php'; $loader =

We try to deploy APC user-cache in a high load environment as local 2nd-tier cache on each server for our central caching service (redis), for caching database queries with rarely changing results, and configuration. We basically looked at what Facebook did (years ago): http://www.slideshare.net/guoqing75/4069180-caching-performance-lessons-from-facebook http://www.slideshare.net/shire/php-tek-2007-apc-facebook It works pretty well for some time, but after some hours under high load, APC runs into problems, so the whole mod_php does not execute any PHP anymore. Even a simple PHP script with

On one page I am doing multiple AJAX calls. All calls return responses successfully but the last one (not related to other ajax calls) returns 500 internal server error as response code (as firebug tells). However, in spite of error code, correct content is returned from that AJAX call. To my amazement, when I set display_errors option in php.ini as On, the error disappears and response in rendered on the page. I have setup error logging to a file but no error is logged corresponding to the above mentioned internal server error. By the way, I am using Apache, JQuery, PHP5, APC (if it is

I've encounter a problem with PHP to store intermediate result locally. With APC ： apc_store("foo", "bar"); $ret = apc_fetch("foo"); With APCu ： apcu_store("foo", "bar", 0); $ret = apcu_fetch("foo"); I store with apc_store/apcu_store under php_cli on a php script, and fetch with apc_fetch/apcu_fetch on another php script, and find the $ret to be empty. While, with shmop : $shmKey = ftok(__FILE__, 't'); $shmId = shmop_open($shmKey, "c", 0644, 1024); $dataArray = array("foo" => "bar"); shmop_write($shmId, serialize($dataArray), 0); $retArray = unserialize(shmop_read($shmId, 0, shmop_size($shmId)

I'm working on a Windows workstation, on which I use WampServer as my development platform, to write PHP applications which are then run on Linux. I'm pretty used to APC on Linux, which is blazing fast and a must have for me. However, I'm always surprised to get no performance gain when I use it on Windows. This leads to generation times close to 1 second per page, on applications relying heavily on the Zend Framework for example. Most of this time is spent parsing PHP files (I verified that by benchmarking include() s). The very same application can run 10x faster on Linux on MacOS. The

I'm trying to find best way to log visits using PHP. Right now I have about 3000 request per second and I write each visit to CSV file. I was wondering is it faster to log each visit in memory somehow and then dump it to CSV file after 100 000 records? I've checked shmop apc and memcache so far but can't find proper solution. The best way is to use Lua with shared memory to store log entries, then create a timer which checks the size of logged entries every X seconds and uses a co-socket to dump the cache to a file or sql database. Should all be non-blocking. And yes you can pass requests to