Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126169
Content-Type: text/plain;
	charset=utf-8
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\))
Subject: Re: [PHP-DEV] Discussion: Remove file statcache?
In-Reply-To: <CADU7aoteX=S1mhsOVPdAu6Qmb+0zAOsgrkAuUdpXV8qAt7n2sw@mail.gmail.com>
Date: Sun, 22 Dec 2024 11:54:52 -0400
Cc: Jakub Zelenka <bukka@php.net>,
 Larry Garfield <larry@garfieldtech.com>,
 php internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <209D4AA4-99BD-4861-B1A4-1BEB80DD3CF2@cmpct.info>
References: <27531d9d-9bfe-4acc-b9ab-80b1017e3038@app.fastmail.com>
 <CAEKnhAFU32EXh483QzR0LLUt+Jou4ejKjOXqBQ_G43wR7LW5cA@mail.gmail.com>
 <e8736456-218d-4a55-a595-e1346e1c6d20@app.fastmail.com>
 <CAEKnhAEAXCmnqfCEyqJbJWr-=XRDY31m2eJDA3WmX9HcA8a0kg@mail.gmail.com>
 <CAEKnhAF3=MzxtaHKtEchhPfm03=Ae_EqgZHQ3LUY=qdcH_+JJg@mail.gmail.com>
 <CADU7aoteX=S1mhsOVPdAu6Qmb+0zAOsgrkAuUdpXV8qAt7n2sw@mail.gmail.com>
To: =?utf-8?Q?K=C3=A9vin_Dunglas?= <kevin@dunglas.fr>
From: calvin@cmpct.info (Calvin Buckley)

On Dec 22, 2024, at 10:57=E2=80=AFAM, K=C3=A9vin Dunglas =
<kevin@dunglas.fr> wrote:
>=20
> On Sun, Dec 22, 2024 at 10:44=E2=80=AFAM Jakub Zelenka <bukka@php.net> =
wrote:
> Thinking about it, there might be a possibility to address it (at =
least on Linux) using fanotify. Not sure about other platforms but maybe =
there are some solutions to address it. Also it might get a bit complex =
and not sure how much the solution is viable.
>=20
> For FrankenPHP, we successfully use https://github.com/e-dant/watcher =
for this kind of usage. It supports Linux (fanotify, notify, epoll...), =
macOS, and Windows, and is very efficient.
> It's a C++ library but with pure C bindings.
>=20
> Best,

I think watching files makes sense for FrankenPHP's use case of
development server, but I can't imagine the overhead and
non-portability makes sense for the stat cache. I feel any gains you'd
have from stat cache would be offset by that. And it'd be unfortunately
the only way to actually solve the "external thing changes thing behind
the stat cache's back" problem.=