mariadb: memory tuning should respect device total RAM
Open
Nobody has claimed this yet.
release/21.02
stale
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: @miska
Environment: OpenWrt 21.02, OpenWrt master
Description:
Copy&þasted from: @VojtechMyslivec
Currently, we provide one static my.cnf mariadb config for the mysqld server.
There are some hardcoded values that should be tuned according to a device total available RAM. i.e. on a 512 MB MOX, there should be lesser limits than on a 2 GB Omnia.
Also, mysqld parameters should be tunable by a user, preferably through uci config.
Originally located on CZ.NIC GitLab.
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 package's static my.cnf configuration and reviewing how OpenWrt packages expose settings through UCI. Define completion as memory-related mysqld limits adapting to device RAM and user-tunable parameters being available through UCI, with behavior checked across the mentioned 512 MB and 2 GB devices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mariadb
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100