FPM is maliciously compliant when asked to set opcache.preload

Description

The following FPM configuration:

php_value[opcache.preload] = /app/config/preload.php
php_value[opcache.preload_user] = app

results in phpinfo() advertising that config.

Yet when calling opcache_get_status(), there is no preload_statistics, and there is no performance improvement in the application.

I asked about this here, and was told that's because it is too late: when setting that config value, FPM has already started. If that's the case, I would expect an exception to be thrown, because I can think of a reason to allow editing that setting past a certain point

PHP Version

8.1.7

Operating System

Linux

まず、php_value[opcache.preload] と php_value[opcache.preload_user] を使用して FPM の設定を再現し、その後 phpinfo() と opcache_get_status() を比較します。opcache のプリロード初期化に対して、FPM がこれらの設定をいつ適用するのかを追跡します。完了条件として、プリロード設定が遅すぎるタイミングで適用された場合の動作を定義し、テストする必要があります。