There won't be any major changes like that to APC. Development has moved to 
opcache. See http://pecl.php.net/package/ZendOpcache

Hi Rasmus - thanks for this info.

One more question (because APC will continue to see usage in PHP <5.5).

In order to have a good/better workaround for the current APC code, I would like 
to have good fragmentation stats. You wrote in https://bugs.php.net/bug.php?
id=58510 that "The fragmentation calculation is a bit artificial and may need to 
be updated for 3.1.2 actually."

In SVN, the apc.php code has not seen changes to the fragmentation calc, so I 
guess that never happened. 

To be more explicit, I am working on the following simplified (pseudo)code:

function my_request_shutdown() {
    if (rand(1, 1000) === 1) { #
        fragmentation = code lifted from apc.php
        if (fragmentation > 80) {
            apc_clear_cache();
        }
    }
}
register_shutdown_function('my_request_shutdown');

If the fragmentation code in apc.php is busted, I'm interested in hints to improve 
it. 

Background -- this is for the rather popular Moodle LMS.

Thanks again ~

Are you actually seeing fragmentation issues? Forget what apc.php tells you, are 
you actually seeing performance degradation due to fragmentation? Honestly I have 
never been able to measure any degradation myself even when apc.php tells me the 
cache is highly fragmented.

Yes, we have a busy Moodle installation showing a very significant slowdown in PHP 
execution. This is in a VM so the workload is well-defined: Moodle. All stats were 
normal, except the apc.php script indicating 100% fragmentation.

Apache graceful restart cured both the fragmentation report and the PHP execution 
slowdown.

Correlation is not causation, but it sure is a hint!

Increasing your segment size should help quite a bit then along with a graceful 
every couple of days. And note that opcache works quite well with PHP 5.4 as 
well.