MySQL Experte gesucht um DB auf Raspy zu optimieren

[qler (Gast)]

Hallo Leute,

Mcöhte die MySQL DB auf meinem Raspy 3 optimieren.
Habe dazu 2 Scripts ausprobiert, die mir schon einige Anhaltspunkte 
gegeben habe.
Leider komme ich nicht mit der Meldung unter den Temp_Tables zurecht.
Ich habe doch schon 512MB zugewiesen !!!

Hier mal das Log:

        -- MYSQL PERFORMANCE TUNING PRIMER --
             - By: Matthew Montgomery -

MySQL Version 4.1.22mysql4-log armv7l is EOL please upgrade to MySQL 4.1 or later

Uptime = 0 days 0 hrs 5 min 58 sec
Avg. qps = 4
Total Questions = 1624
Threads Connected = 1

Warning: Server has not been running for at least 48hrs.
It may not be safe to use these recommendations

To find out more information on how each of these
runtime variables effects performance visit:
http://dev.mysql.com/doc/refman/4.1/en/server-system-variables.html
Visit http://www.mysql.com/products/enterprise/advisors.html
for info about MySQL's Enterprise Monitoring and Advisory Service

SLOW QUERIES
The slow query log is NOT enabled.
Current long_query_time = 10 sec.
You have 0 out of 1638 that take longer than 10 sec. to complete
Your long_query_time seems to be fine

BINARY UPDATE LOG
The binary update log is enabled

WORKER THREADS
Current thread_cache_size = 0
Current threads_cached = 0
Current threads_per_sec = 1
Historic threads_per_sec = 0
Your thread_cache_size is fine

MAX CONNECTIONS
Current max_connections = 8
Current threads_connected = 1
Historic max_used_connections = 2
The number of used connections is 25% of the configured maximum.
Your max_connections variable seems to be fine.

INNODB STATUS
Cannot parse InnoDB stats prior to 5.0.x
ERROR 1227 (HY000) at line 1: Access denied; you need the SUPER privilege for this operation
Current innodb_buffer_pool_size = 8 M
Depending on how much space your innodb indexes take up it may be safe
to increase this value to up to 2 / 3 of total system memory

MEMORY USAGE
Max Memory Ever Allocated : 157 M
Configured Max Per-thread Buffers : 12 M
Configured Max Global Buffers : 154 M
Configured Max Memory Limit : 166 M
Physical Memory : 925 M
Max memory limit seem to be within acceptable norms

KEY BUFFER
Current MyISAM index space = 0 bytes
Current key_buffer_size = 16 M
Key cache miss rate is 1 : 2
Key buffer free ratio = 58 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 128 M
Current query_cache_used = 3 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 3.04 %
Current query_cache_min_res_unit = 4 K
Your query_cache_size seems to be too high.
Perhaps you can use these resources elsewhere
MySQL won't cache query results that are larger than query_cache_limit in size

SORT OPERATIONS
Current sort_buffer_size = 512 K
Current read_rnd_buffer_size = 508 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 0 queries where a join could not use an index properly
Your joins seem to be using indexes properly

OPEN FILES LIMIT
Current open_files_limit = 1024 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
Your open_files_limit value seems to be fine

TABLE CACHE
You are not '1002' or 'root'
I am unable to determine the table_count!
Current table_cache value = 256 tables
You have 195 open tables.
The table_cache value seems to be fine

TEMP TABLES
Current max_heap_table_size = 511 M
Current tmp_table_size = 512 M
Of 50 temp tables, 49% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Perhaps you should increase your tmp_table_size and/or max_heap_table_size
to reduce the number of disk-based temporary tables
Note! BLOB and TEXT columns are not allow in memory tables.
If you are using these columns raising these values might not impact your
ratio of on disk temp tables.

TABLE SCANS
Current read_buffer_size = 252 K
Current table scan ratio = 129 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 0 : 1790
Your table locking seems to be fine

 >>  MySQLTuner 1.6.12 - Major Hayden <[e-mail]>
 >>  Bug reports, feature requests, and downloads at http://mysqltuner.com/
 >>  Run with '--help' for additional options and output filtering
[--] Performing tests on 127.0.0.1:3047
[!!] Successfully authenticated with no password - SECURITY RISK!

[--] Skipped version check for MySQLTuner script
[!!] failed to execute: SHOW GLOBAL STATUS
[!!] FAIL Execute SQL / return code: 256
[!!] failed to execute: SHOW SLAVE STATUS\G
[!!] FAIL Execute SQL / return code: 256
[!!] failed to execute: SHOW SLAVE HOSTS
[!!] FAIL Execute SQL / return code: 256
[!!] Your MySQL version 4.1.22mysql4-log is EOL software!  Upgrade soon!
[OK] Operating on 32-bit architecture with less than 2GB RAM

-------- Storage Engine Statistics -----------------------------------------------------------------
[--] Status: -Archive -BDB -Federated +InnoDB -ISAM -NDBCluster
[!!] InnoDB is enabled but isn't being used
[OK] Total fragmented tables: 0

-------- Security Recommendations ------------------------------------------------------------------
[!!] failed to execute: SELECT CONCAT(user, '@', host) FROM mysql.user WHERE TRIM(USER) = '' OR USER IS NULL
[!!] FAIL Execute SQL / return code: 256
[OK] There are no anonymous accounts for any database users
[!!] No more password checks for MySQL version <=5.1
[!!] MySQL version <=5.1 are deprecated and end of support.

-------- CVE Security Recommendations --------------------------------------------------------------
[--] Skipped due to --cvefile option undefined
Argument "du:" isn't numeric in addition (+) at /usr/local/sbin/mysqltuner.pl
        line 2103 (#1)
    (W numeric) The indicated string was fed as an argument to an operator
    that expected a numeric value instead.  If you're fortunate the message
    will identify which operator was so unfortunate.


-------- Performance Metrics -----------------------------------------------------------------------
[--] Up for: 6m 4s (1K q [5.058 qps], 123 conn, TX: 8M, RX: 153K)
[--] Reads / Writes: 97% / 3%
[--] Binary logging is enabled (GTID MODE: OFF)
[--] Physical Memory     : 925.6M
[--] Max MySQL memory    : 678.4M
[--] Other process memory: 61.2M
[--] Total buffers: 666.0M global + 1.6M per thread (8 max threads)
[--] P_S Max memory usage: 0B
[--] Galera GCache Max memory usage: 0B
[OK] Maximum reached memory usage: 669.1M (72.29% of installed RAM)
[OK] Maximum possible memory usage: 678.4M (73.30% of installed RAM)
[OK] Overall possible memory usage with other process is compatible with memory available
[OK] Slow queries: 0% (0/1K)
[OK] Highest usage of available connections: 25% (2/8)
[OK] Aborted connections: 0.00%  (0/123)
[OK] Query cache efficiency: 26.9% (214 cached / 797 selects)
[OK] Query cache prunes per day: 0
[OK] Sorts requiring temporary tables: 0% (0 temp sorts / 84 sorts)
[OK] No joins without indexes
[!!] Temporary tables created on disk: 98% (49 on disk / 50 total)
[OK] Table cache hit rate: 97% (195 open / 201 opened)
[OK] Open file limit used: 37% (386/1K)
[OK] Table locks acquired immediately: 100% (1K immediate / 1K locks)
[OK] Binlog cache memory access: 0% ( 0 Memory / 0 Total)

-------- ThreadPool Metrics ------------------------------------------------------------------------
[--] ThreadPool stat is disabled.

-------- Performance schema ------------------------------------------------------------------------
[--] Performance schema is disabled.

-------- MyISAM Metrics ----------------------------------------------------------------------------
[!!] Key buffer used: 41.8% (7M used / 16M cache)
[!!] Cannot calculate MyISAM index size - re-run script as root user

-------- AriaDB Metrics ----------------------------------------------------------------------------
[--] AriaDB is disabled.

-------- InnoDB Metrics ----------------------------------------------------------------------------
[--] InnoDB is disabled.

-------- TokuDB Metrics ----------------------------------------------------------------------------
[--] TokuDB is disabled.

-------- Galera Metrics ----------------------------------------------------------------------------
[--] Galera is disabled.

-------- Replication Metrics -----------------------------------------------------------------------
[--] Galera Synchronous replication: NO
[--] No replication slave(s) for this server.
[--] This is a standalone server.

-------- Recommendations ---------------------------------------------------------------------------
General recommendations:
    Add skip-innodb to MySQL configuration to disable InnoDB
    MySQL started within last 24 hours - recommendations may be inaccurate
    Enable the slow query log to troubleshoot bad queries
    Temporary table size is already large - reduce result set size
    Reduce your SELECT DISTINCT queries without LIMIT clauses
    Upgrade to MySQL 5.5+ to use asynchronous write

Und hier meine My.cfg:

# The following options will be passed to all MySQL clients
[client]
#password       = your_password
port            = 3047
socket          = /usr/local/mysql4/var/mysqld.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port                            = 3047
socket                          = /usr/local/mysql4/var/mysqld.sock
skip-locking
key_buffer                      = 16M
max_allowed_packet              = 1M
table_cache =                   256
sort_buffer_size                = 512K
net_buffer_length               = 8K
read_buffer_size                = 256K
read_rnd_buffer_size            = 512K
myisam_sort_buffer_size         = 8M
tmp-table-size                  = 512M
max-heap-table-size             = 512M
query-cache-type                = 1
query-cache-size                = 128M
max-connections                 = 8


# Replication Master Server (default)
# binary logging is required for replication
log-bin
expire-logs-days               = 14
sync-binlog                    = 1

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id       = 1

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

Auf dem Raspy 3 läuft nur der MySQL4 Server für ein Buchaltungsprogramm.
Sonst nix.
Es kann also der Speicher so gut wie möglich ausgenutzt werden.

Was kann ich da noch optimieren?

[Peter II (Gast)]

qler schrieb:
> Was kann ich da noch optimieren?

Ich würde bei der Indizierung anfangen. Nimm dir eine Anfrage die lange 
dauert und schau welche Spalten und Tabellen beteiligt sind.

(Es stellt sich mir aber die Frage, warum man nun den langsamsten PC für 
so etwas verwenden muss, für die Zeit die du jetzt investieren muss, 
könnte man auch einen etwas schnelleren PC hinstellen. Wo auch die 
Datenspeicher sinnvoll angebunden ist)

[qler (Gast)]

Weil der Rapsy 3 eben nur um die 5 Watt braucht.

Meine grösste Frage ist eben die folgige:
Wie behebe ich folgende Meldung:

[!!] Temporary tables created on disk: 98% (49 on disk / 50 total)

[S R (Gast)]

MAX_HEAP_TABLE_SIZE und TMP_TABLE_SIZE erhöhen.

Nutze auch mal tuning-primer.sh, das ist etwas detaillierter.

Besser wäre es den Grund für die temporären Tabellen zu beseitigen 
(sinnvoll Indizes vergeben...)

[Peter II (Gast)]

qler schrieb:
> Weil der Rapsy 3 eben nur um die 5 Watt braucht.

und?

http://www.shuttle.eu/de/produkte/nano/nc01u/spezifikation/

Verlustleistung: Leerlauf: 5,5 W, Volllast: 11,6 / 22,4 W (ohne/mit 
Grafik)


die Raspis sind zwar schön und gut, aber sie sind langsam!. Netzwerk und 
Festplatte hängen an einem gemeinsamen USB 2.0.

Ich mache auch einiges damit, aber wenn man eine Datenbank betreibt wo 
du vermutlich nicht mal an den Datenstrukturen etwas ändern kannst sind 
sie nicht ideal.

[S R (Gast)]

tmp-table-size                  = 512M
max-heap-table-size             = 512M


das ist doch quatsch. Schau mal, wie die Bezeichner wirklich heißen.

[S R (Gast)]

qler schrieb:
> MySQL Version 4.1.22mysql4-log armv7l is EOL please upgrade to MySQL 4.1
> or later

Das 4.1 scheint mir auch ein wenig alt?

[Axel S. (a-za-z0-9)]

qler schrieb:
> Mcöhte die MySQL DB auf meinem Raspy 3 optimieren.

Warum? Ist sie (zu) langsam oder was?

> Leider komme ich nicht mit der Meldung unter den Temp_Tables zurecht.

Ja. Das passiert, wenn man Werkzeuge zu verwenden versucht, die man 
nicht verstanden hat. Freundlicherweise hat Matthew ja noch einen 
möglichen Grund hingeschrieben, warum eine Temptable materialisiert 
wird, obwohl ausreichend RAM dafür konfiguriert wurde. Bist du dem 
eigentlich mal nachgegangen?

Außerdem: es wurden in 5 Minuten Uptime 50 Temptables angelegt. Also 
eine alle 6 Sekunden. Glaubst du ernsthaft, daß das deinen Raspi 
überlastet?

> Was kann ich da noch optimieren?

Falsche Frage.

Die richtige Frage ist: Sollte ich überhaupt etwas optimieren? Und die 
Antort ist in der Regel: Nein. Falls es eine andere Antwort gibt, dann 
kannst du die sicher begründen. Und dann können wir weiter sehen.

[Karli (Gast)]

Hallo zusammen,

Habe das selbe Problem, das zuviele Temp Tables angelegt werden (um die 
1300). Auf einem Raspi 3. Es wird auch CAO benutzt.
Gibt es da schon eine My.cnf, welche vernüftig optimiert ist (bezüglich 
den Temptbles) ??????

[Karli (Gast)]

Das ist meine Config:

[mysqld]
port                            = 3007
socket                          = /usr/local/mysql4/var/mysqld.sock
skip-locking
key_buffer                      = 128M
max_allowed_packet              = 1M
table_cache                     = 256
sort_buffer_size                = 4M
read_buffer_size                = 4M
join_buffer_size                = 2M
net_buffer_length               = 8K
read_rnd_buffer_size            = 4M
myisam_sort_buffer_size         = 64M
tmp_table_size                  = 512M
max_heap_table_size             = 512M
query_cache_type                = 1
query_cache_size                = 128M
query_cache_limit               = 128M
thread_concurrency              = 8
max_connections                 = 4