From 78cff893e7ade029a2ba35eb5924bba2390832d8 Mon Sep 17 00:00:00 2001 From: Adrien Crivelli Date: Sat, 28 Sep 2024 18:31:08 +0200 Subject: [PATCH] Update _posts/14-03-01-Object-Caching.md Co-authored-by: Chris Brown --- _posts/14-03-01-Object-Caching.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/14-03-01-Object-Caching.md b/_posts/14-03-01-Object-Caching.md index 694fa85..da883a3 100644 --- a/_posts/14-03-01-Object-Caching.md +++ b/_posts/14-03-01-Object-Caching.md @@ -23,7 +23,7 @@ hyper-fast data store in a central location and many different systems can pull 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 exists for the duration of the command. So you have to be mindful of your +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