Bug #76280 [Com]: Performance degrades permantly when overwriting PHP files, until apache restart

From: Date: Mon, 23 Nov 2020 19:31:19 +0000
Subject: Bug #76280 [Com]: Performance degrades permantly when overwriting PHP files, until apache restart
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-230551@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=76280&edit=1

 ID:                 76280
 Comment by:         rtrtrtrtrt at dfdfdfdf dot dfd
 Reported by:        teo8976 at gmail dot com
 Summary:            Performance degrades permantly when overwriting PHP
                     files, until apache restart
 Status:             No Feedback
 Type:               Bug
 Package:            opcache
 Operating System:   debian
 PHP Version:        5.6.36
 Assigned To:        cmb
 Block user comment: N
 Private report:     N

 New Comment:

> That is the current behavior?? 
> If that wasted memory never gets freed, that sounds like a bug to me.

no, that's by design to avoid memory fragmentation which has it's own problems like APC
had with it - in theory a ton of cache memory free but no free segment large enough to cache
anything useful anymore


Previous Comments:
------------------------------------------------------------------------
[2020-11-23 18:06:15] cmb@php.net

Consider to read <http://blog.jpauli.tech/2015-03-05-opcache-html/>.

------------------------------------------------------------------------
[2020-11-23 17:49:25] php4fan at gmail dot com

> if updated files are being cached by OPcache, the old files
> will never be removed from the shared memory (this is reporteded
> as wasted memory).  This wasted memory may sum up to the point
> where you no longer have sufficient free memory, so no more files
> can be cached, what would cause them to be executed uncached.

That is the current behavior?? If that wasted memory never gets freed, that sounds like a bug to me.

I haven't tested PHP 7 yet.

------------------------------------------------------------------------
[2020-11-22 04:22:08] php-bugs at lists dot php dot net

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.

------------------------------------------------------------------------
[2020-11-09 17:28:25] cmb@php.net

Is this still an issue with any of the actively supported PHP
versions[1]?

If so: if updated files are being cached by OPcache, the old files
will never be removed from the shared memory (this is reporteded
as wasted memory).  This wasted memory may sum up to the point
where you no longer have sufficient free memory, so no more files
can be cached, what would cause them to be executed uncached.
That might explain the behavior you've described.

[1] <https://www.php.net/supported-versions.php>

------------------------------------------------------------------------
[2018-04-28 15:27:04] teo8976 at gmail dot com

> the most lkiley problem is that your configuration don't suite your workload

Let's assume this is the case.

That would explain a TEMPORARY degradation in performance.

Even if that is justified by a bad configuration which is my fault, if that doesn't recover on
its own after a while that no file is being changed, then there's a bug.

> pretty clear says you never gave a damn about your configs

Indeed, I never did. But again, if I need to worry about fine-tuning my configs just for PHP to be
stable, then it's ill-designed.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=76280


--
Edit this bug report at https://bugs.php.net/bug.php?id=76280&edit=1


Thread (16 messages)

« previous php.bugs (#230551) next »