|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #77980 why remove --disable-opcache-filecache
Submitted: 2019-05-07 11:02 UTC Modified: 2019-05-07 11:31 UTC
From: spam2 at rhsoft dot net Assigned:
Status: Not a bug Package: opcache
PHP Version: Next Major Version OS:
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: spam2 at rhsoft dot net
New email:
PHP Version: OS:


 [2019-05-07 11:02 UTC] spam2 at rhsoft dot net
how does the fact that something is no longer experimental justify bloated binaries with unused code? frankly i don't want having "systemctl reload httpd" not clear the opcache and i don't want bloatet binaries

if you want to to do something useful move the core into a loadable so-file instead have it twice in /usr/bin/php and /usr/lib64/httpd/modules/ and make both a tiny shim-loader


Remove --disable-opcache-filecache option
This is no longer an experimental feature, and we have the ability
to control this at runtime via an ini setting.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2019-05-07 11:07 UTC]
-Status: Open +Status: Wont fix
 [2019-05-07 11:08 UTC]
-Status: Wont fix +Status: Not a bug
 [2019-05-07 11:08 UTC]
Because nobody ever tests the --disable-opcache-filecache build and IIRC it was broken at the time due to a missing #ifdef. A marginally smaller binary is not a reason to keep around this option. This does not make up any significant part of the binary.
 [2019-05-07 11:12 UTC] spam2 at rhsoft dot net
it makes a significant part of the binary and testing these days is the job of a computer and not humans 

we use that option since it exists *because* it makes significant smaller and it was never broken except maybe PHP7.3 which is curently out-of-scope here given the large amout of bugs which slowly go in a direction to call it "stable"
 [2019-05-07 11:31 UTC]
Please provide specific numbers for the significant size increases you are seeing, as well as which compile options they were produced under.
 [2019-05-07 11:33 UTC] spam2 at rhsoft dot net
around 20% with a highly optimized PGO build as far as i remember
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun Mar 03 05:01:28 2024 UTC