php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

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
Votes:1
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
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: laph at gmx dot de
New email:
PHP Version: OS:

 

 [2010-09-16 19:37 UTC] 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.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2010-09-16 20:01 UTC] rasmus@php.net
-Status: Open +Status: Wont fix
 [2010-09-16 20:01 UTC] rasmus@php.net 
Impossible without massive architecture changes.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Dec 21 15:01:29 2024 UTC