nextcloud / nextcloud/serverinfo

MyISAM key buffer peak usage low

Open
#1,133 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
JavaScript
Stars
130
Forks
64
Avg merge
1d 1h
Merged PRs (30d)
49

Description

Image

Similar here:
my instance: Value 0.0046
TP: Value 0

Both: key_buffer_size = 64M

What is a good recommendation/change?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached screenshot and the reported MyISAM key buffer values for the instance and TP, then trace where this metric is collected and displayed in the repository. Done means identifying whether the low peak usage is expected or incorrectly reported and documenting or implementing a clearly agreed change.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
observability-sre
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.