The WordPress code base has outgrown the defaults for opcache.memory_consumption and opcache.interned_strings_buffer

Description

The WordPress code base has been growing, and it's now too big for the OPcache default sizes.

In php8.3 (on Ubuntu at any rate), the defaults, as you know, are (in MiB):

opcache.memory_consumption=128 
opcache.interned_strings_buffer=8

WordPress 6.9.4 and 7.0beta4 both run these caches completely full for relatively simple sites. That means a typical WordPress site isn't getting all the benefit of caching, which hammers performance and frustrates server operators and site owners.

I respectfully suggest you double the memory_consumption default in future releases. And triple the interned_strings_buffer default. If you can do it, this change will, as it spreads out, save lots of server power and it will reduce carbon emissions.

(I'm working on a Site Health Check feature for WordPress to inform site owners about this issue. It's harder to communicate with server operators.)

https://github.com/rlerdorf/opcache-status shows the problem clearly on any site.

Comienza con los valores predeterminados de configuración de opcache.memory_consumption y opcache.interned_strings_buffer en el código fuente de PHP; el issue no identifica ningún archivo ni prueba. Revisa los valores reportados de PHP 8.3 y usa la herramienta opcache-status enlazada para reproducir el uso de la caché. Se considera completado cuando los valores predeterminados propuestos se hayan evaluado y estén cubiertos por las pruebas de configuración relevantes.