Your message dated Sat, 25 Mar 2023 16:28:24 -0700
with message-id
<caou6tad97ygzs+p3ejdpgujknuwnknmnccab2gdrv81_0xo...@mail.gmail.com>
and subject line Re: [debian-mysql] Bug#925385: /usr/bin/mysql: Poor MariaDB
performance
has caused the Debian Bug report #925385,
regarding /usr/bin/mysql: Poor MariaDB performance
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
925385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925385
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mariadb-client-core-10.1
Version: 10.1.37-0+deb9u1
Severity: important
File: /usr/bin/mysql
Dear Maintainer,
I am working on a Tinkerboard
(https://www.asus.com/us/Single-Board-Computer/Tinker-Board/), which is an ARM
dev-board. The board has a Cortex-A17 1.4 GHz cpu, 2 GB RAM, and 16 GB SDcard.
The board runs Debian 9.8.
I have a program that tries to use MySQL, but MySQL/MariaDB is mostly unusable
on this board due to poor performance.
I installed the following packages (and recommends) and ran
mysql_secure_installation. Everything else is a Debian default.
* mysql-server
* mysql-client
* mysql-utilities
* libmariadbd-dev
The test program/SQL below attempts to create two small tables and two users.
It takes 13 seconds to complete. I've read about the changes Debian made to
MySQL at
https://mariadb.com/kb/en/library/moving-from-mysql-to-mariadb-in-debian-9/,
but I don't know what is causing this problem. This is not my area of expertise.
The smae program and SQL runs fine on Fedora 29 and dev-boards. Performance is
about where one expects, give or take.
The command to setup the test database is:
# Password set using mysql_secure_installation
$ time mysql -uroot -pZZZZZZZZZZZZZZZZZZZZZZZZZZZZ < testdb.sql
real 0m12.799s
user 0m0.040s
sys 0m0.000s
The contents of testdb.sql are:
DROP DATABASE IF EXISTS testdb;
CREATE DATABASE IF NOT EXISTS testdb;
USE testdb;
#####################################################
CREATE TABLE IF NOT EXISTS name_number
(
`nn_id` INT PRIMARY KEY AUTO_INCREMENT,
`nn_name` VARCHAR(64) CHARACTER SET utf8,
`nn_number` VARCHAR(18) CHARACTER SET utf8
);
CREATE INDEX IF NOT EXISTS number_index ON name_number(nn_number);
#####################################################
CREATE TABLE IF NOT EXISTS whitelist
(
`list_id` INT PRIMARY KEY AUTO_INCREMENT,
`nn_id` INT NOT NULL,
`list_date` DATETIME,
FOREIGN KEY fk1_id (nn_id)
REFERENCES name_number(nn_id)
);
#####################################################
CREATE TABLE IF NOT EXISTS blacklist
(
`list_id` INT PRIMARY KEY AUTO_INCREMENT,
`nn_id` INT NOT NULL,
`list_date` DATETIME,
FOREIGN KEY fk2_id (nn_id)
REFERENCES name_number(nn_id)
);
#####################################################
CREATE USER IF NOT EXISTS 'testdb_admin'@'localhost' IDENTIFIED BY
'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX';
CREATE USER IF NOT EXISTS 'testdb_admin'@'%' IDENTIFIED BY
'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX';
CREATE USER IF NOT EXISTS 'testdb_user'@'localhost' IDENTIFIED BY
'YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY';
CREATE USER IF NOT EXISTS 'testdb_user'@'%' IDENTIFIED BY
'YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY';
GRANT ALL PRIVILEGES ON testdb.* TO 'testdb_admin'@'localhost';
GRANT ALL PRIVILEGES ON testdb.* TO 'testdb_admin'@'%';
GRANT SELECT,INSERT,UPDATE,DELETE ON testdb.* TO 'testdb_user'@'localhost';
GRANT SELECT,INSERT,UPDATE,DELETE ON testdb.* TO 'testdb_user'@'%';
-- System Information:
Debian Release: 9.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)
Kernel: Linux 4.4.132+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mariadb-client-core-10.1 depends on:
ii libaio1 0.3.110-3
ii libc6 2.24-11+deb9u4
ii libncurses5 6.0+20161126-1+deb9u2
ii libreadline5 5.2+dfsg-3+b1
ii libstdc++6 6.3.0-18+deb9u1
ii libtinfo5 6.0+20161126-1+deb9u2
ii mariadb-common 10.1.37-0+deb9u1
ii zlib1g 1:1.2.8.dfsg-5
mariadb-client-core-10.1 recommends no packages.
mariadb-client-core-10.1 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I did not see any follow-up on this so I will close the bug as it has
action items to do.
On Mon, 6 Mar 2023 at 23:33, Otto Kekäläinen <[email protected]> wrote:
>
> Hi!
>
> Latest version of MariaDB in Debian unstable/testing/Bookworm is
> 10.11.2. You might want to consider testing it.
>
> If you want to contribute in the open source way to fix this or any
> other issue, see
> https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
> on how to submit a Merge Request!
>
>
> If you have time to help, please consider these (in order of importance):
>
> 1. Review current open MRs at
> https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests
>
> 2. Review items highlighted by Debian QA systems (Lintian, builds etc)
> and submit a fix to improve the quality:
> https://tracker.debian.org/pkg/mariadb
>
> 3. Review what testing we have at
> https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines and
> think about potential gaps - CI is very important as it is the only
> way we can prevent regressions in a scalable way
>
> 4. Review/follow-up on existing bugs that currently need more
> information:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=mariadb&src=mariadb-10.6&src=mariadb-10.5&src=mariadb-10.3&src=mariadb-10.1
>
> MariaDB and C++ skills are useful, but not required. For example
> reviewing the NEWS for 10.11 requires no coding skills:
> https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/37
>
>
> My request for help from debian-devel in
> https://lists.debian.org/debian-devel/2023/02/msg00272.html did not
> get many responses, so the future of this package depends on how
> active the users and people who previously reported bugs are in
> participating in the maintenance of the package.
>
> - Otto
--- End Message ---
