exclude path

[anonymous]

Hi!
Can exclude some php script from optimiser?
Like eaccelerator.filter="" in eaccelerator or apc.filters in APC?
Thanks.

[anonymous]

yeah, but any reason yet? in case if it's not because some script cannot be cached properly

[judas_iscariote]

I think this may be an alternative to considere, however. if and script do not compile or cache properly, please post it here, that needs to be fixed, reliability is one of top priorites.
Im spending a great amount of time testing too :)

[anonymous]

i use php application, then create very much (more then 100.000) .php files, which used for cache purpose. These files contain very simple php code, which changes every 1-2 hour and don’t need additional acceleration.

[litkaj]

It is worth mentioning that you can exclude entire directories using an .htaccess file. You need to add the following lines:

php_flag xcache.cacher Off
php_flag xcache.optimizer Off

[Nneel]

xclude path ? means particular folder(s) ?
if its needed to exclude few scripts in a folder but not the folder?

[CyberCr33p]

If you run php 5.3.x and want to exclude a folder from xcache you can create a .user.ini and add:

xcache.cacher=0

[bestis]

6 years and nothing. I cannot see how ignoring folders would help in cases
where the ignored file is in folder you want cache. Also think the file
as a config file that can be generated by the program itself.

Then you want to reduce stat() calls by telling:
xcache.stat = "Off"

But now, once your config file it's cached, it's cached. Program can't
change it's settings without someone clearing the cache. Not nice.

For example in eAccelerator I can have:
eaccelerator.check_mtime = 0
eaccelerator.filter = "!*liteconf.php !*datafiles/config* *.php"

I see that I could put .htaccess to datafiles/config to ignore it, but
can't do anything with ignore of *liteconf.php as that folder has files
needed to cache.

I don't know how many users have similar use cases as mine is, but
before this enhancement is done, we can't use Xcache.

[moo]

thanks for asking. i'll implement lazy stat first after 2.0.1 is released. see #253
some reasons (like avoiding encoded file) to use filter was eliminated, some later IMHO