Skip to content

Commit 538390d

Browse files
committed
enh(admin_manual): update OPcache JIT docs
Single Nextcloud instances have shown to use less than 2 MiB of the configured JIT buffer size, so that 8 MiB is sufficient by a large margin. Using any larger value pre-occupies the `opcache.memory_consumption` accurdingly and 128 MiB would hence fill its default 128 MiB completely, without any benefit. The example JIT size is hence reduced to 8 MiB. Enabling JIT however has shown to raise overall OPcache usage by a larger amount than the configured JIT size, so that `opcache.memory_consumption` might still need to be raised in some cases. This information is added to the documentation: nextcloud/all-in-one#2755 (comment) Additionally, the info is added that JIT is currently supported on x86 platforms only. Signed-off-by: MichaIng <[email protected]>
1 parent 791c2bb commit 538390d

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

admin_manual/installation/server_tuning.rst

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ However, the revalidation frequency can be adjusted and may *potentially* enhanc
146146

147147
.. danger::
148148
Lengthening the time between revalidation (or disabling it completely) means that manual changes to scripts, including ``config.php``, will take longer before they become active (or will never do so, if
149-
revalidation is disabled completely). Lengthening also increases the likelihood of transient Server and application upgrade problems. It also prevents the proper toggling of maintenance mode.
149+
revalidation is disabled completely). Lengthening also increases the likelihood of transient server and application upgrade problems. It also prevents the proper toggling of maintenance mode.
150150

151151
.. warning::
152152
If you adjust these parameters, you are more likely to need to restart/reload your web server (mod_php) or fpm after making configuration changes or performing upgrades. If you forget to do so, you
@@ -189,12 +189,17 @@ Nextcloud strictly requires code comments to be preserved in opcode, which is th
189189
JIT
190190
^^^
191191

192-
PHP 8.0 and above ship with a JIT compiler that can be enabled to benefit any CPU intensive apps you might be running. To enable a tracing JIT with all optimizations:
192+
PHP 8.0 and above ship with a JIT compiler that can be enabled on x86 platforms to benefit any CPU intensive apps you might be running. To enable a tracing JIT with all optimizations:
193193

194194
.. code:: ini
195195
196196
opcache.jit = 1255
197-
opcache.jit_buffer_size = 128M
197+
opcache.jit_buffer_size = 8M
198+
199+
.. note::
200+
201+
Single Nextcloud instances have shown to use less than 2 MiB of the configured JIT buffer size, so that 8 MiB is sufficient by a large margin. The overall OPcache usage however raises by a larger amount, so that ``opcache.memory_consumption`` might need to be raised in some cases. The Nextcloud admin panel will then show a related warning.
202+
JIT buffer usage can be monitored with `opcache-gui <https://github.com/amnuts/opcache-gui>`_ as well.
198203

199204
Previews
200205
--------

0 commit comments

Comments
 (0)