blocks|key|2089608|text|所有php工作人员与父php进程共享相同的操作码缓存；来源。如果您有一个/apc_clear_cache.php文件，并在HTTP上调用该文件(使用类似curl的内容)，您将使用相同的php主进程为所有工作人员清除操作码缓存。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2089609|这个博客文章很好地解释了apc是如何工作的，以及如何在发布期间有效地清除它。|2089610|entityMap|0|LINK|mutability|MUTABLE|url|http://news.php.net/php.internals/63539|1|http://blog.wepay.com/weploy-wepays-deployment-tool/^0|R|2|0|0|2|4|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

All the php-fpm workers share the same opcode cache as the parent php-fpm process; <a href="http://news.php.net/php.internals/63539" rel="nofollow">source</a>. If you have a /apc_clear_cache.php file and you call that over HTTP (using something like curl), you will clear the opcode cache for all workers using the same php-fpm master process.

This <a href="http://blog.wepay.com/weploy-wepays-deployment-tool/" rel="nofollow">blog article</a> has a very good explanation of how apc works and how to clear it effectively during release.

blocks|key|2089647|text|我刚刚发现不同的池也共享相同的APC缓存，至少在PHP+5.4中与FPM共享，就操作码缓存内容而言。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2089648|我就是这样注意到的：|2089649|我设置了多个PHP池，每个池位于/srv/www/domain.com/目录下。|2089650|PHP脚本的主要位置是/srv/www/domain.com/docroot/。|2089651|现在，如果我创建一个文件/srv/www/domain_1.com/docroot/test.php，并加载脚本，它将显示它应该显示的内容。|2089652|但是，当我创建/srv/www/domain2.com/docroot/test.php文件时，内容也显示在domain_1.com下面。|2089653|我认为这是因为APC使用文件位置作为缓存的密钥，在这两种情况下，键是/docroot/test.php。|2089654|清除操作码缓存可能仅限于单个池。不过，我还没测试过这个。|2089655|编辑清除操作码缓存不会被重新分配到一个应用程序池中，当调用apc_cache_clear()时，会清除完整的APC缓存。|2089656|我还尝试使用apc.mmap_file_mask为每个池指定不同的掩码。这并没有改变任何事情，一个应用程序池文件中的更新出现在其他程序池中。|2089657|在apc.stat=0环境下观察到了这种行为。使用lsyncd监视对文件的所有更改，迫使APC缓存中的条目重新编译。|2089658|泰罗|unordered-list-item|2089659|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|16|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|17|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|18|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|19|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1A|8|@]|9|@]|A|$]]|$1|V|3|W|5|X|7|1B|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|Z|$]]

I have just found out that different pools also share the same APC cache, at least in PHP 5.4 with FPM and as far as the opcode cache content is concerned.

This is how I noticed it:

I have set up multiple PHP-FPM pools, where each pool is chrooted under /srv/www/domain.com/ directory.

The main location for PHP scripts is /srv/www/domain.com/docroot/.

Now, if I create a file /srv/www/domain_1.com/docroot/test.php, and load the script, it shows what it should show.

However, when I create the file /srv/www/domain_2.com/docroot/test.php, the contents show also up under domain_1.com.

I think this happens because APC uses the file location as the key for its cache, and in both cases the key is /docroot/test.php.

Clearing the opcode cache might be restricted only to a single pool. I haven't tested this though.

EDIT Clearing the opcode cache isn't restircted to a single app pool, the complete APC cache is cleared when apc_cache_clear() is called.

I also tried to use apc.mmap_file_mask to specify a different mask for every pool. This didn't change anything, updates in one app pool files were seen in other pools.

This behaviour was observed with apc.stat=0 setting. All changes to files are monitored with lsyncd, forcing a recompile of the entry in APC cache.

<ul>
<li>Tero</li>
</ul>

blocks|key|1612466|text|如果您通过FastCGI接口直接执行脚本，您可以通过cli清除操作码缓存，而无需将文件部署到您的网站。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1612467|我已经创建了这个要旨，您可以在服务器上使用它来清除php5-fpm缓存。|offset|length|1612468|如果您使用的是unix套接字：|1612469|php+clear-apc.php+--sock+/var/run/php5-fpm.sock|style|CODE|1612470|否则：|1612471|php+clear-apc.php+--port=[port]|1612472|或省略默认的127.0.0.1:9000|1612473|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/stuartcarnie/5523506^0|0|6|4|0|0|0|0|1B|0|0|0|V|0|6|E|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@$D|11|E|12|1|13]]|A|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|15|8|@$D|16|E|17|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|19|8|@$D|1A|E|1B|J|K]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1C|8|@$D|1D|E|1E|J|K]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

You can clear the opcode cache via the cli without having to deploy the files to your website if you execute the script via the FastCGI interface directly.

I've created <a href="https://gist.github.com/stuartcarnie/5523506">this gist</a> which you can use on your servers to clear the php5-fpm cache.

If you're using unix sockets:

<code>php clear-apc.php --sock /var/run/php5-fpm.sock</code>

Otherwise:

<code>php clear-apc.php --port=[port]</code>

or omit for default <code>127.0.0.1:9000</code>

Internet has a lot of discussions that calling <code>apc_cache_clear()</code> in CLI does not clear opcode caches from "web" PHP processes, whether they are run inside Apache or by FPM (see <a href="https://stackoverflow.com/questions/911158/how-to-clear-apc-cache-entries">How to clear APC cache entries?</a> ). As a suggested solution, it's possible to create a simple PHP page that calls <code>apc_cache_clear()</code>, and call that from CLI. <a href="https://github.com/ornicar/ApcBundle" rel="nofollow noreferrer">Symfony's ApcBundle</a> does that.

If the <code>apc_cache_clear()</code> from CLI does not empty the cache from Apache/FPM, does it between FPM workers? If I call /clear_apc_cache.php over HTTP, it's run by only by one of the FPM worker processes. So, is the APC opcode cache really shared between pools and workers - and more specific: is it cleared from all workers automatically?

Is APC opcode cache shared between PHP-FPM pools/workers?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

Internet上有很多讨论，认为在CLI中调用apc_cache_clear()并不能清除来自"web“PHP进程的操作码缓存，无论它们是在Apache内部运行还是由FPM运行(参见 )。作为建议的解决方案，可以创建一个调用apc_cache_clear()的简单PHP页面，然后从CLI调用它。就是这么做的。如果来自...

问PHP池/工作人员之间是否共享APC操作码缓存？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问PHP池/工作人员之间是否共享APC操作码缓存？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问PHP池/工作人员之间是否共享APC操作码缓存？
EN