real_path_cache design
| From: | lists@rhsoft.net | Date: | Mon, 19 Jun 2017 13:01:04 +0000 |
| Subject: | real_path_cache design | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-99545@lists.php.net to get a copy of this message | ||
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