|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #52865 Opcode Cachers (APC, Xcache) don't respect worker pools
Submitted: 2010-09-16 19:37 UTC Modified: 2010-09-16 20:01 UTC
Avg. Score:3.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: laph at gmx dot de Assigned:
Status: Wont fix Package: FPM related
PHP Version: 5.3.3 OS: Debian Linux x64
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Bug Type:
From: laph at gmx dot de
New email:
PHP Version: OS:


 [2010-09-16 19:37 UTC] laph at gmx dot de
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

Expected result:
The fpm-sapi should be able to configure opcode caches on a worker-pool basis through php_value[]/php_flag's.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2010-09-16 20:01 UTC]
-Status: Open +Status: Wont fix
 [2010-09-16 20:01 UTC]
Impossible without massive architecture changes.
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Sat Jan 28 04:03:49 2023 UTC