Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99545
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender)
To: PHP internals <internals@lists.php.net>
Message-ID: <4d54d365-9db4-f94d-f899-19aae762c596@rhsoft.net>
Date: Mon, 19 Jun 2017 15:01:04 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: de-CH
Content-Transfer-Encoding: 7bit
Subject: real_path_cache design
From: lists@rhsoft.net ("lists@rhsoft.net")

can someone take a look at https://bugs.php.net/bug.php?id=73888

real_path_cache as it is implemented now is pretty worthless when each 
worker maintains it's own cache and clearstatcache() can not work at all 
with that design because the worker which calls clearstatcache() doe sit 
for it's own "instance" of the cache and the others don't know anyhting 
about it

https://github.com/php/php-src/commit/782b84c6d550ac6e695b54070bb0b409cac29f58 
also does more harm than benfits because you waste 4 MB for each worker 
process with a still unpredictable and mostly low hitrate

under growing load with a high number of workers the problem grows, low 
hitrate and clearstatcache() on a just changed file with no effect for 
any of the other worker processes