Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126161
Feedback-ID: i8414410d:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Sat, 21 Dec 2024 22:05:20 -0600
To: "php internals" <internals@lists.php.net>
Message-ID: <e072b4ff-a695-4f06-b05b-5393535d2a93@app.fastmail.com>
In-Reply-To: <062201db53e5$7c7043f0$7550cbd0$@glaive.pro>
References: <27531d9d-9bfe-4acc-b9ab-80b1017e3038@app.fastmail.com>
 <062201db53e5$7c7043f0$7550cbd0$@glaive.pro>
Subject: Re: [PHP-DEV] Discussion: Remove file statcache?
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: larry@garfieldtech.com ("Larry Garfield")

On Sat, Dec 21, 2024, at 2:18 PM, Juris Evertovskis wrote:
> While it is nice the Symfony and WordPress wouldn't suffer a lot from
> dropping this cache, what's the impact on scripts that are processing
> hundreds of files?
>
> Would doing ` $stat = stat($filename);` instead of separate calls to
> `filemtime` and `filesize` actually be important? Or would it still amount
> to 1% performance difference on an SSD?

The limited data so far suggests it isn't that important, unless you're doing filemtime(), filesize() together in order over hundreds or thousands of files.  In that case, calling stat() would be better, though by how much is unclear.  Or using SplFileInfo().  (I have no idea if it uses the stat cache or loads the stat data once and just exposes it through methods.)

> I mean, are there cases when this cache is still useful in 2025?

That is indeed the question. :-)  I think so far we can say "not most of the time," but haven't yet figured out all the possible edge cases.

--Larry Garfield