nextcloud / nextcloud/nextcloudpi

Optimize database with mysqlcheck

Open
#989 4 comments 2 reactions 1 assignee View on GitHub

@nachoparker is already working on this.

Since Sep 6, 2019.

enhancement good first issue has-updates
Dominant language
Shell
Stars
2.9k
Forks
318
PR merge metrics
No merged PRs in 30d

Description

After running NC with NCP for more then a year with over 2 million files stored on it, I asked myself if the mysql/mariadb DB needs to be maintained?
I searched the internet and the simplest solution I found was using

sudo mysqlcheck -o --all-databases

This reduced the DB size from around 950MB to a little over 800MB and NC seems to be a little more responsive (but this could homeopathic as well)

Any, would it make sens to extend NCP with an "DB Optimize" option?

5 Days after the optimization plus an upgrade to NC 16.0.4 I am still under 850MB. I am fetching the information via ocs_data_server_database_size provided by serverinfo.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.