Currently, the UI allows tuning only opcache.memory_consumption, but not opcache.interned_strings_buffer, which is critical for performance on large or high-traffic insurance websites (https://insurancecoverage.site). The default 8 MB buffer can quickly become a bottleneck, causing lower hit rates even when total OPcache memory is high. Allowing this setting in the UI (e.g., 8 MB, 16 MB, 32 MB) would align with best practices and prevent interned string exhaustion. This would significantly improve cache efficiency and overall performance.
Currently, the UI allows tuning only opcache.memory_consumption, but not opcache.interned_strings_buffer, which is critical for performance on large or high-traffic insurance websites (https://insurancecoverage.site). The default 8 MB buffer can quickly become a bottleneck, causing lower hit rates even when total OPcache memory is high. Allowing this setting in the UI (e.g., 8 MB, 16 MB, 32 MB) would align with best practices and prevent interned string exhaustion. This would significantly improve cache efficiency and overall performance.