[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#539131: marked as done (mysqltuner - wrong InnoDB statistics)

Your message dated Fri, 15 Dec 2023 22:10:00 +0100
with message-id <ZXzAqBwxD8ZDF1IN@cord.de>
and subject line Re: Bug#539131: mysqltuner - wrong InnoDB statistics
has caused the Debian Bug report #539131,
regarding mysqltuner - wrong InnoDB statistics
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 owner@bugs.debian.org
immediately.)


-- 
539131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539131
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: mysqltuner
Version: 0.9.0
Severity: normal

MySQLTuner worngly report InnoDB statistics for data and index usage.

If I check my MySQL with following SQL I get different data:

mysql> SELECT engine, sum(table_rows) as table_rows, (sum(data_length)/1048576) as data_length, (sum(index_length)/1048576) as index_length, (sum(data_length + index_length)/1048576) as total_length FROM information_schema.tables WHERE table_schema NOT IN ('information_schema', 'mysql') GROUP BY engine ORDER BY table_schema;
+--------+------------+-------------+--------------+--------------+
| engine | table_rows | data_length | index_length | total_length |
+--------+------------+-------------+--------------+--------------+
| MyISAM |    5316014 |    710.9443 |     160.0234 |     870.9678 |
| InnoDB |   33084457 |   2744.9688 |    2054.8125 |    4799.7813 |
+--------+------------+-------------+--------------+--------------+


MySQLTuner report following statistics:

-------- General Statistics --------------------------------------------------

[--] Unable to check for the latest MySQLTuner version
[OK] Currently running supported MySQL version 5.0.51a-24+lenny1-log
[OK] Operating on 64-bit architecture

-------- Storage Engine Statistics -------------------------------------------
[--] Status: +Archive -BDB -Federated +InnoDB -ISAM -NDBCluster
[--] Data in MyISAM tables: 710M (Tables: 120)
[--] Data in InnoDB tables: 2G (Tables: 15)

-------- Performance Metrics -------------------------------------------------
[--] Up for: 2d 1h 5m 25s (5M q [31.390 qps], 258K conn, TX: 2B, RX: 546M)
[--] Reads / Writes: 69% / 31%
[--] Total buffers: 1.7M per thread and 5.1G global
[OK] Maximum possible memory usage: 5.4G (69% of installed RAM)
[OK] Slow queries: 1% (105K/5M)
[OK] Highest usage of available connections: 23% (47/200)
[OK] Key buffer size / total MyISAM indexes: 1.0G/160.1M
[OK] Key buffer hit rate: 99.4%
[!!] Query cache efficiency: 17.5%
[!!] Query cache prunes per day: 3160
[!!] Sorts requiring temporary tables: 16%
[!!] Temporary tables created on disk: 41%
[OK] Thread cache hit rate: 99%
[!!] Table cache hit rate: 0%
[OK] Open file limit used: 7%
[OK] Table locks acquired immediately: 99%
[OK] InnoDB data size / buffer pool: 2.7G/4.0G


Diffrences are in 'Data in InnoDB tables: 2G' which is in fact 2.7G and 'InnoDB data size / buffer pool: 2.7G/4.0G' is wrongly calculated because in InnoDB buffer pool are both data and indexes so threre should be smth like 'InnoDB structures size / buffer pool: 4.7G/4.0G'.


-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages mysqltuner depends on:
ii  perl                          5.10.0-19  Larry Wall's Practical Extraction 

Versions of packages mysqltuner recommends:
ii  mysql-server           5.0.51a-24+lenny1 MySQL database server (metapackage
ii  mysql-server-5.0 [mysq 5.0.51a-24+lenny1 MySQL database server binaries

mysqltuner suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hallo! Antonin Faltynek hat geschrieben:

I just uploaded a new version of mysqltuner. 

Your bug report is rather old, and mysql 5.0.51 is long outdated. So i'll
close this report. If it persists with current mysqltuner and a more recent
MySQL please file a new bug.

> [OK] Currently running supported MySQL version 5.0.51a-24+lenny1-log

> ii  mysql-server           5.0.51a-24+lenny1 MySQL database server (metapackage
> ii  mysql-server-5.0 [mysq 5.0.51a-24+lenny1 MySQL database server binaries

thank you,
	Cord

--- End Message ---
Reply to: