-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use var PHP_OPCACHE_MEMORY_CONSUMPTION for configuration #2090
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Thomas Clavier <tom@tcweb.org>
Signed-off-by: Thomas Clavier <tom@tcweb.org>
I think maybe using "sed" to change original files? |
using |
Sorry, That all version was build by template files, your code is right. |
This requires some documentation in the README. |
RUN { \ | ||
echo 'opcache.enable=1'; \ | ||
echo 'opcache.interned_strings_buffer=32'; \ | ||
echo 'opcache.max_accelerated_files=10000'; \ | ||
echo 'opcache.memory_consumption=128'; \ | ||
echo 'opcache.memory_consumption=${PHP_OPCACHE_MEMORY_CONSUMTION}'; \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
echo 'opcache.memory_consumption=${PHP_OPCACHE_MEMORY_CONSUMTION}'; \ | |
echo 'opcache.memory_consumption=${PHP_OPCACHE_MEMORY_CONSUMPTION}'; \ |
@@ -95,7 +96,7 @@ RUN { \ | |||
echo 'opcache.enable=1'; \ | |||
echo 'opcache.interned_strings_buffer=32'; \ | |||
echo 'opcache.max_accelerated_files=10000'; \ | |||
echo 'opcache.memory_consumption=128'; \ | |||
echo 'opcache.memory_consumption=${PHP_OPCACHE_MEMORY_CONSUMTION}'; \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
echo 'opcache.memory_consumption=${PHP_OPCACHE_MEMORY_CONSUMTION}'; \ | |
echo 'opcache.memory_consumption=${PHP_OPCACHE_MEMORY_CONSUMPTION}'; \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're going to support opcache changes like this, we should probably also support opcache.max_accelerated_files
and opcache.interned_strings_buffer
since they're all part of the same setup checks in Server. Otherwise it'll be an incomplete enhancement.
See also #2185 (comment) |
@@ -20,6 +20,7 @@ RUN set -ex; \ | |||
# see https://docs.nextcloud.com/server/stable/admin_manual/installation/source_installation.html | |||
ENV PHP_MEMORY_LIMIT 512M | |||
ENV PHP_UPLOAD_LIMIT 512M | |||
ENV PHP_OPCACHE_MEMORY_CONSUMTION 128 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ENV PHP_OPCACHE_MEMORY_CONSUMTION 128 | |
ENV PHP_OPCACHE_MEMORY_CONSUMPTION 128 |
@@ -79,11 +79,12 @@ RUN set -ex; \ | |||
# see https://docs.nextcloud.com/server/latest/admin_manual/installation/server_tuning.html#enable-php-opcache | |||
ENV PHP_MEMORY_LIMIT 512M | |||
ENV PHP_UPLOAD_LIMIT 512M | |||
ENV PHP_OPCACHE_MEMORY_CONSUMTION 128 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ENV PHP_OPCACHE_MEMORY_CONSUMTION 128 | |
ENV PHP_OPCACHE_MEMORY_CONSUMPTION 128 |
This is a common request downstream in nextcloud/helm. If this PR was re-submitted with the suggested fixes here, would it still be viable? I see there was conversation #2185, but I can't tell if that means this PR should be closed? |
Is it only about the |
see also #2275 |
No description provided.