nextcloud/nextcloudpi

Optimize database with mysqlcheck

Open

#989 opened on Sep 4, 2019

View on GitHubContributor guide
 (4 comments) (2 reactions) (1 assignee)Shell (320 forks)auto 404
enhancementgood first issuehas-updates

Repository metrics

Stars
 (2,920 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Explore integration of mysqlcheck into NextcloudPi's management interface, possibly via a new menu option or scheduled cron job.
Tech stack
shellmysql
Domain
devopsdatabase
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ShellMySQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65