Skip to content
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

do not display the buffer_size info if the size is already set to a c… #32902

Merged
merged 1 commit into from
Jun 21, 2022

Conversation

szaimen
Copy link
Contributor

@szaimen szaimen commented Jun 16, 2022

…ertain threshold

Signed-off-by: szaimen [email protected]

@szaimen szaimen added enhancement 3. to review Waiting for reviews labels Jun 16, 2022
@szaimen szaimen added this to the Nextcloud 25 milestone Jun 16, 2022
@szaimen szaimen requested a review from MichaIng June 16, 2022 15:53
@szaimen szaimen marked this pull request as ready for review June 16, 2022 15:54
@szaimen
Copy link
Contributor Author

szaimen commented Jun 16, 2022

@MichaIng WDYT? :)

@szaimen szaimen force-pushed the enh/noid/opcache-buffer-size-limit branch from f617b4e to cd3d7ce Compare June 16, 2022 16:00
@MichaIng
Copy link
Member

MichaIng commented Jun 16, 2022

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 opcache.memory_consumption / 4 (32 MiB with default OPcache size of 128 MiB) for this reason: nextcloud/all-in-one#791 (comment)

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.

@szaimen szaimen force-pushed the enh/noid/opcache-buffer-size-limit branch from cd3d7ce to dd49c45 Compare June 17, 2022 11:15
@szaimen
Copy link
Contributor Author

szaimen commented Jun 17, 2022

All right! then lets do it like suggested. Does this look good now? :)

@szaimen szaimen requested review from artonge, a team, blizzz, skjnldsv and CarlSchwan and removed request for a team June 17, 2022 11:22
…ertain threshold

Signed-off-by: szaimen <[email protected]>
Co-Authored-By: MichaIng <[email protected]>
@szaimen szaimen force-pushed the enh/noid/opcache-buffer-size-limit branch from 700a47f to f8bebb6 Compare June 17, 2022 20:15
@szaimen szaimen requested a review from MichaIng June 17, 2022 20:22
@szaimen szaimen requested a review from PVince81 June 20, 2022 18:08
@szaimen
Copy link
Contributor Author

szaimen commented Jun 21, 2022

CI failure unrelated

@szaimen szaimen merged commit fb4353b into master Jun 21, 2022
@szaimen szaimen deleted the enh/noid/opcache-buffer-size-limit branch June 21, 2022 11:26
@szaimen
Copy link
Contributor Author

szaimen commented Jun 21, 2022

/backport to stable24

@szaimen
Copy link
Contributor Author

szaimen commented Jun 21, 2022

/backport to stable23

@backportbot-nextcloud
Copy link

The backport to stable23 failed. Please do this backport manually.

@backportbot-nextcloud
Copy link

The backport to stable24 failed. Please do this backport manually.

@MichaIng
Copy link
Member

The backport to stable23 failed. Please do this backport manually.

Strange, the code line and lines around are identical on all three branches 🤔.

@szaimen
Copy link
Contributor Author

szaimen commented Jun 21, 2022

lets try again

@szaimen
Copy link
Contributor Author

szaimen commented Jun 21, 2022

/backport to stable24

@szaimen
Copy link
Contributor Author

szaimen commented Jun 21, 2022

/backport to stable23

@backportbot-nextcloud
Copy link

The backport to stable24 failed. Please do this backport manually.

@backportbot-nextcloud
Copy link

The backport to stable23 failed. Please do this backport manually.

@szaimen szaimen restored the enh/noid/opcache-buffer-size-limit branch June 21, 2022 17:07
@szaimen szaimen deleted the enh/noid/opcache-buffer-size-limit branch June 21, 2022 17:14
MichaIng added a commit that referenced this pull request Jan 20, 2023
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 <[email protected]>
nextcloud-command pushed a commit that referenced this pull request Jan 23, 2023
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 <[email protected]>
backportbot-nextcloud bot pushed a commit that referenced this pull request Jan 23, 2023
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 <[email protected]>
backportbot-nextcloud bot pushed a commit that referenced this pull request Jan 23, 2023
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 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants