info/php-the-right-way
1
0
Fork 0
mirror of https://github.com/codeguy/php-the-right-way.git synced 2025-08-06 14:06:34 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #1011 from PowerKiKi/patch-1

Browse Source 
Precision on when APCu cache is shared or not
This commit is contained in:
Xymph
2024-09-30 11:52:49 +02:00
committed by GitHub
parent ef9bc49a20 78cff893e7
commit 630628d17c
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
_posts/14-03-01-Object-Caching.md
View File

@@ -20,9 +20,11 @@ one real limitation of APCu is that it is tied to the server it's installed on.
installed as a separate service and can be accessed across the network, meaning that you can store objects in a
hyper-fast data store in a central location and many different systems can pull from it.
Note that when running PHP as a (Fast-)CGI application inside your webserver, every PHP process will have its own cache,
i.e. APCu data is not shared between your worker processes. In these cases, you might want to consider using memcached
instead, as it's not tied to the PHP processes.
Note that whether the cache is shared across PHP processes depends on how PHP is used. When running PHP via PHP-FPM,
the cache is shared across all processes of all pools. When running PHP as a (Fast-)CGI application inside your
webserver, the cache is not shared, i.e every PHP process will have its own APCu data. When running PHP as a command
line, the cache is not shared and will only exist for the duration of the command. So you have to be mindful of your
situation and goals. And you might want to consider using memcached instead, as it's not tied to the PHP processes.
In a networked configuration APCu will usually outperform memcached in terms of access speed, but memcached will be
able to scale up faster and further. If you do not expect to have multiple servers running your application, or do not