Bug #52865 [Opn->Wfx]: Opcode Cachers (APC, Xcache) don't respect worker pools
| From: | rasmus@php.net | Date: | Thu, 16 Sep 2010 18:01:29 +0000 |
| Subject: | Bug #52865 [Opn->Wfx]: Opcode Cachers (APC, Xcache) don't respect worker pools | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-154437@lists.php.net to get a copy of this message | ||
Edit report at http://bugs.php.net/bug.php?id=52865&edit=1
ID: 52865
Updated by: rasmus@php.net
Reported by: laph at gmx dot de
Summary: Opcode Cachers (APC, Xcache) don't respect worker
pools
-Status: Open
+Status: Wont fix
Type: Bug
Package: FPM related
Operating System: Debian Linux x64
PHP Version: 5.3.3
Block user comment: N
New Comment:
Impossible without massive architecture changes.
Previous Comments:
------------------------------------------------------------------------
[2010-09-16 19:37:06] laph at gmx dot de
Description:
------------
When using either APC or Xcache with the FPM sapi, it seems to be
impossible to configure - (de-)activate, set cache sizes, etc. - them on
a "per worker-group" level.
The cachers are either active or inactive on a global level - through
apc.ini or xcache.ini in the "additional ini files dir" - and all worker
pools share the same (one) memory-segment and configuration.
In this case the benefit of the fpm sapi is gone, (well, reduced at
least...)
I'm using the Debian Packages from dotdeb.org.
Expected result:
----------------
The fpm-sapi should be able to configure opcode caches on a worker-pool
basis through php_value[]/php_flag's.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/bug.php?id=52865&edit=1