OPcache backlist

[Remi Collet]

Hi,

Using the new Zend OPcache, starting with php 5.5.0beta3, I'm going to
push today in rawhide and F19, you can specify a list of files that
should not be accelerated.
> From upstream comments

; Files are usually triggered by one of the following three reasons:
; 1) Directories that contain auto generated code, like Smarty or ZFW cache.
; 2) Code that does not work well when accelerated, due to some delayed
;    compile time evaluation.
; 3) Code that triggers an OPcache bug.

In RPM default provided configuration:

opcache.blacklist_filename=/etc/php.d/opcache*.blacklist

So, you can provide, in your package, if needed:

For exemple
Name:
    /etc/php.d/opcache-horde.blacklist

Content;
     /etc/horde/

Of course, this file could be provided in all branches, including EPEL,
as php-pecl-zendopcache will be provided there (as soon as review,
please, if you have some time), with the same default configuration.

Remi.

[Remi Collet]

Le 11/04/2013 07:47, Remi Collet a écrit :
> For exemple
> Name:
>    /etc/php.d/opcache-horde.blacklist
>
> Content;
>     /etc/horde/

Another way to manage cache for configuration file is to use the new
"opcache_invalidate" function (PHP 5.5.0bet3 or ZendOpcache 7.0.2, not
yet released)

Examples:
https://github.com/horde/horde/pull/44
https://forge.indepnet.net/projects/glpi/repository/revisions/20742/diff

Remi.