nextcloud / nextcloud/nextcloudpi
Opcache Settings via NCP
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
Description
The error message The OPcache interned strings buffer is nearly full. in Nextcloud, starting with NC23, was the reason to dig a little deeper into the problem and I found this thread
https://help.nextcloud.com/t/nextcloud-23-02-opcache-interned-strings-buffer/134007
As far as I have understood, with NC23 it is capable of giving you recommendations for settings to be changed based on the individual usage of the server. In my case the opcache was full therefore the recommendation was to increase opcache.interned_strings_buffer
This was as not a problem for me to do manually, but this setting should be added to the nc-limits in ncp-web / ncp-cli.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the nc-limits implementation in ncp-web and ncp-cli, then read how existing OPcache settings are exposed. Add opcache.interned_strings_buffer to both interfaces and verify that the setting appears in their limits or configuration output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100