Uh oh!
There was an error while loading. Please reload this page.
do not display the buffer_size info if the size is already set to a c… - #32902
Conversation
szaimen
commented
Jun 16, 2022
@MichaIng WDYT? :) |
Uh oh!
There was an error while loading. Please reload this page.
f617b4e to
cd3d7ceCompareUh oh!
There was an error while loading. Please reload this page.
Generally I agree that with the probably rare but existing (and summing) cases where the interned strings buffer seems to be used without limits by Nextcloud only, we need to mute the warning at some point. At least until someone finds time to deeper investigate under which circumstances or by which app this wasteful interned strings buffer usage is triggered. I however suggest to raise it to Not using a hardcoded value here would cover cases where other applications are used aside of Nextcloud on the same FPM pool. In this case, the OPcache may need to be raised above the default (never the case with Nextcloud only), and then a higher interned strings buffer also becomes more reasonable. The other way round I personally use only 64 MiB OPcache size with a small Nextcloud instance (also not many apps) and in this case 32 MiB interned strings (in my case ~3.5 MiB used only) doesn't seem to be reasonable, 16 MiB seem a better limit then for muting the warning. |
cd3d7ce to
dd49c45CompareAll right! then lets do it like suggested. Does this look good now? :) |
Uh oh!
There was an error while loading. Please reload this page.
…ertain threshold Signed-off-by: szaimen <szaimen@e.mail.de> Co-Authored-By: MichaIng <micha@dietpi.com>
700a47f to
f8bebb6Compareszaimen
commented
Jun 21, 2022
CI failure unrelated |
szaimen
commented
Jun 21, 2022
/backport to stable24 |
szaimen
commented
Jun 21, 2022
/backport to stable23 |
The backport to stable23 failed. Please do this backport manually. |
The backport to stable24 failed. Please do this backport manually. |
MichaIng
commented
Jun 21, 2022
Strange, the code line and lines around are identical on all three branches 🤔. |
szaimen
commented
Jun 21, 2022
lets try again |
szaimen
commented
Jun 21, 2022
/backport to stable24 |
szaimen
commented
Jun 21, 2022
/backport to stable23 |
The backport to stable24 failed. Please do this backport manually. |
The backport to stable23 failed. Please do this backport manually. |
With #32902 it was meant to be avoided to recommend raising the interned strings buffer size above a quarter of the total OPcache size. This works as long as there is at least 1 byte free, but does not apply if the buffer is filled completely. This commit switches the conditions so that the interned strings buffer size must be smaller than a quarter of the total OPcache size for the warning to be shown. That the buffer must be either filled completely or by more than 90% remains untouched. Signed-off-by: MichaIng <micha@dietpi.com>
With #32902 it was meant to be avoided to recommend raising the interned strings buffer size above a quarter of the total OPcache size. This works as long as there is at least 1 byte free, but does not apply if the buffer is filled completely. This commit switches the conditions so that the interned strings buffer size must be smaller than a quarter of the total OPcache size for the warning to be shown. That the buffer must be either filled completely or by more than 90% remains untouched. Signed-off-by: MichaIng <micha@dietpi.com>
With #32902 it was meant to be avoided to recommend raising the interned strings buffer size above a quarter of the total OPcache size. This works as long as there is at least 1 byte free, but does not apply if the buffer is filled completely. This commit switches the conditions so that the interned strings buffer size must be smaller than a quarter of the total OPcache size for the warning to be shown. That the buffer must be either filled completely or by more than 90% remains untouched. Signed-off-by: MichaIng <micha@dietpi.com>
With #32902 it was meant to be avoided to recommend raising the interned strings buffer size above a quarter of the total OPcache size. This works as long as there is at least 1 byte free, but does not apply if the buffer is filled completely. This commit switches the conditions so that the interned strings buffer size must be smaller than a quarter of the total OPcache size for the warning to be shown. That the buffer must be either filled completely or by more than 90% remains untouched. Signed-off-by: MichaIng <micha@dietpi.com>
…ertain threshold
Signed-off-by: szaimen szaimen@e.mail.de