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

go to bug id or search bugs for

Bug #58053 apc slow/fragmented after apache kills childprocess
Submitted: 2008-02-21 15:41 UTC Modified: 2009-03-23 14:23 UTC
From: erik at samson-it dot nl Assigned:
Status: Closed Package: APC (PECL)
PHP Version: 5.2.0 OS: server 2003
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: erik at samson-it dot nl
New email:
PHP Version: OS:

 

 [2008-02-21 15:41 UTC] erik at samson-it dot nl 
Description:
------------
It's APC 3.0.17 that we're using actually. 

But the bug: we've seen that after apache kills a child process and creates a new one, the APC-status page shows a very high fragmentation (80+ %) and the website using the APC-cache gets very slow. 

Now i'm wondering if there's anybody else who can reproduce this or it's just us who experience this problem.
Of course ideally we would like apache not to kill it's childprocess, but it does. So why does it affect APC?

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2008-02-22 04:46 UTC] erik at samson-it dot nl 
after manually restarting the apache-windowsservice apc is of course totally refreshed and working fine, until the first child process is killed.
 [2009-03-22 21:21 UTC] shire@php.net 
We've optimized the fragmentation so this should no longer slow down your server.  Please try latest CVS and let us know if this does/does not fix your problem.

I'd be interested to know if you do see fragmentation jumps when children processes are killed though as this could be another issue.  If so please let us know how you're tracking this and if the children are being killed by timeouts, or as part of apache's limit on requests served etc. Thanks.
 [2009-03-23 03:10 UTC] erik at samson-it dot nl 
thanks for the reply, but we are no longer using APC as an 
opcode cache. since there seems to be nobody who can 
reproduce this behaviour and i'm not able to reproduce this 
anymore, this bug can be closed for me.
 [2009-03-23 14:23 UTC] shire@php.net 
Thank you for the update, again sorry for the long delay in getting back to this.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri May 17 10:01:32 2024 UTC