Jumping on this bandwagon. On a relatively busy instance I need to use these values to get rid of the warning. Not a PHP expert at all, but I was increasing them until the error went away, using whatever PHP was complaining about until i get it green. NC version 29, 10 active users, NC used mostly via browser for office work/emails/deck/ and additionally around 100GB traffic between users / day.

opcache.enable=1
opcache.enable_cli=1
opcache.interned_strings_buffer=64
opcache.max_accelerated_files=12000
opcache.memory_consumption=512
opcache.save_comments=1
opcache.revalidate_freq=60
opcache.jit = 1255
opcache.jit_buffer_size = 256M

Hello @adripo @tzerber
I have the same issue. I actually struggle to locate the file php.ini within the Nextcloud container.
Any pointers?
Thanks !

Hello @adripo @tzerber
I have the same issue. I actually struggle to locate the file php.ini within the Nextcloud container.
Any pointers?
Thanks !

Depends if you're using docker or not. Usually phpinfo() can give you hints on ini location

Depends if you're using docker or not. Usually phpinfo() can give you hints on ini location

I use Docker indeed
the image linked to this repo https://hub.docker.com/_/nextcloud/

Depends if you're using docker or not. Usually phpinfo() can give you hints on ini location

I use Docker indeed the image linked to this repo https://hub.docker.com/_/nextcloud/

For opcache I use the following mounted local ini in all containers :

volumes:
      - nextcloud:/var/www/html
      - ./opcache-recommed.ini:/usr/local/etc/php/conf.d/opcache-recommended.ini

The actual conf used by the container is this one /usr/local/etc/php-fpm.conf and it loads everything from /usr/local/etc/php/conf.d/*conf too. Both those paths are !! Inside !! the container, not on your host!

@tzerber

opcache.jit_buffer_size = 256M

Try to use opcache.jit_buffer_size = 2M. I never saw a Nextcloud instance which uses more than 1 MiB of this particular sub-buffer. And since it occupies from opcache.memory_consumption, it is likely the only reason why you needed to raise the latter, while otherwise the default 128M would have been sufficient, in combination with opcache.interned_strings_buffer=32 max, often 8 or 16, depending on used apps.