Optymalizacja MYSQL'a - VPS

[peres.pro 9]

Witam bardzo serdecznie, chciałbym abyście pomogli mi zoptymalizować mysql na moim VPSie. Posiadam pakiet MAX w livenet.pl - http://livenet.pl/en...?serwery-vps,15

 

O to log z mysqltunera:

>>  MySQLTuner 1.2.0 - Major Hayden <major@mhtx.net>
>>  Bug reports, feature requests, and downloads at http://mysqltuner.com/
>>  Run with '--help' for additional options and output filtering
[OK] Logged in using credentials from debian maintenance account.

-------- General Statistics --------------------------------------------------
[--] Skipped version check for MySQLTuner script
[OK] Currently running supported MySQL version 5.5.25a-1~dotdeb.1-log
[!!] Switch to 64-bit OS - MySQL cannot currently use all of your RAM

-------- Storage Engine Statistics -------------------------------------------
[--] Status: +Archive -BDB -Federated +InnoDB -ISAM -NDBCluster
[--] Data in MyISAM tables: 546K (Tables: 109)
[--] Data in InnoDB tables: 3M (Tables: 159)
[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 17)
[--] Data in MEMORY tables: 0B (Tables: 2)
[!!] Total fragmented tables: 168

-------- Security Recommendations  -------------------------------------------
[!!] User '@localhost' has no password set.
[!!] User '@s2.lanceq.eu' has no password set.

-------- Performance Metrics -------------------------------------------------
[--] Up for: 1h 55m 44s (9K q [1.360 qps], 566 conn, TX: 7M, RX: 2M)
[--] Reads / Writes: 32% / 68%
[--] Total buffers: 192.0M global + 2.7M per thread (151 max threads)
[OK] Maximum possible memory usage: 597.8M (11% of installed RAM)
[OK] Slow queries: 0% (2/9K)
[OK] Highest usage of available connections: 5% (9/151)
[OK] Key buffer size / total MyISAM indexes: 16.0M/303.0K
[OK] Key buffer hit rate: 99.9% (16K cached / 17 reads)
[OK] Query cache efficiency: 66.3% (1K cached / 2K selects)
[OK] Query cache prunes per day: 0
[OK] Sorts requiring temporary tables: 0% (0 temp sorts / 7 sorts)
[OK] Temporary tables created on disk: 18% (64 on disk / 340 total)
[OK] Thread cache hit rate: 98% (9 created / 566 connections)
[OK] Table cache hit rate: 25% (316 open / 1K opened)
[OK] Open file limit used: 26% (272/1K)
[OK] Table locks acquired immediately: 99% (2K immediate / 2K locks)
[OK] InnoDB data size / buffer pool: 3.9M/128.0M

-------- Recommendations -----------------------------------------------------
General recommendations:
Run OPTIMIZE TABLE to defragment tables for better performance
MySQL started within last 24 hours - recommendations may be inaccurate

 

A tutaj my.cnf

 

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port  = 3306
socket  = /var/run/mysqld/mysqld.sock
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket  = /var/run/mysqld/mysqld.sock
nice  = 0[mysqld]
#
# * Basic Settings
#
user  = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket  = /var/run/mysqld/mysqld.sock
port  = 3306
basedir  = /usr
datadir  = /var/lib/mysql
tmpdir  = /tmp
# lc-message-dir is unknown to MySQL 5.1
#lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
#bind-address  = 127.0.0.1
#
# * Fine Tuning
#
key_buffer  = 16M
max_allowed_packet = 16M
thread_stack  = 192K
thread_cache_size	   = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover		 = BACKUP
#max_connections		= 100
#table_cache			= 64
#thread_concurrency	 = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size		= 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file		= /var/log/mysql/mysql.log
#general_log			 = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
slow_query_log = 1
slow_query_log_file = /var/log/mysql/mysql-slow.log
long_query_time = 3
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#	   other settings you may need to change.
#server-id  = 1
#log_bin   = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size		 = 100M
#binlog_do_db  = include_database_name
#binlog_ignore_db = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
#no-auto-rehash # faster start of mysql but no tab completition[isamchk]
key_buffer  = 16M
#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/

Edytowano Sierpień 4, 2012 przez lanceq (zobacz historię edycji)

[N0Name 48]

A to tak ciężko wpisać 2-3 wyrazy w google? np. Optymalizacja mysql Debian6.

[peres.pro 9]

A to tak ciężko wpisać 2-3 wyrazy w google? np. Optymalizacja mysql Debian6.

 

Szukałem, niestety mam VPS'a a te tematy są o dedykach, tak trudno doświadczonej osobie poświęcić te 2 minuty i wskazać co jest źle/dobrze itp. ?

 

A tutaj jeszcze wypowiedź pewnego Administratora z serwisu forum.ovh.pl jakby Ci było mało:

 

Nie ma przykładowego configa, ponieważ są to sprawy indywidualne dla każdej bazy. Wystarczy sprowadzić wyniki do odpowiednich wartości.

 

Następny razem jak będziesz wyganiał do google'a to sprawdź czy to tam faktycznie jest okej ?

Edytowano Sierpień 5, 2012 przez lanceq (zobacz historię edycji)

[SanKen 63]

Po pierwsze masz wyraźnie napisane że testy robi się po 24 godzinach... Nikt nic ci ciekawego nie powie na temat optymalizacji jeśli jest to od razu po uruchomieniu serwera. Pozostaw domyślne i czekać na swój czas.

 

ps. napisz co ty tam masz i czy używasz innodb? Jeśli nie można wyłączyć.

Edytowano Sierpień 5, 2012 przez SanKen (zobacz historię edycji)

[peres.pro 9]

Po pierwsze masz wyraźnie napisane że testy robi się po 24 godzinach... Nikt nic ci ciekawego nie powie na temat optymalizacji jeśli jest to od razu po uruchomieniu serwera. Pozostaw domyślne i czekać na swój czas.

 

ps. napisz co ty tam masz i czy używasz innodb? Jeśli nie można wyłączyć.

 

 

Proszę bardzo, uptime ponad 1 dzień. Do tego na moich stronach jest prawie zerowy ruch.

 

root@s1:/home# ./mysqltuner.pl
>>  MySQLTuner 1.2.0 - Major Hayden <major@mhtx.net>
>>  Bug reports, feature requests, and downloads at http://mysqltuner.com/
>>  Run with '--help' for additional options and output filtering
[OK] Logged in using credentials from debian maintenance account.
-------- General Statistics --------------------------------------------------
[--] Skipped version check for MySQLTuner script
[OK] Currently running supported MySQL version 5.5.25a-1~dotdeb.1-log
[!!] Switch to 64-bit OS - MySQL cannot currently use all of your RAM
-------- Storage Engine Statistics -------------------------------------------
[--] Status: +Archive -BDB -Federated +InnoDB -ISAM -NDBCluster
[--] Data in MyISAM tables: 546K (Tables: 109)
[--] Data in InnoDB tables: 5M (Tables: 170)
[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 17)
[--] Data in MEMORY tables: 0B (Tables: 2)
[!!] Total fragmented tables: 179
-------- Security Recommendations  -------------------------------------------
[!!] User '@localhost' has no password set.
[!!] User '@s2.lanceq.eu' has no password set.
-------- Performance Metrics -------------------------------------------------
[--] Up for: 1d 7h 7m 38s (93K q [0.830 qps], 3K conn, TX: 68M, RX: 29M)
[--] Reads / Writes: 47% / 53%
[--] Total buffers: 192.0M global + 2.7M per thread (151 max threads)
[OK] Maximum possible memory usage: 597.8M (11% of installed RAM)
[OK] Slow queries: 0% (2/93K)
[OK] Highest usage of available connections: 8% (13/151)
[OK] Key buffer size / total MyISAM indexes: 16.0M/303.0K
[OK] Key buffer hit rate: 100.0% (215K cached / 24 reads)
[OK] Query cache efficiency: 52.0% (18K cached / 35K selects)
[!!] Query cache prunes per day: 7285
[OK] Sorts requiring temporary tables: 0% (0 temp sorts / 320 sorts)
[OK] Temporary tables created on disk: 24% (161 on disk / 652 total)
[OK] Thread cache hit rate: 99% (16 created / 3K connections)
[OK] Table cache hit rate: 25% (331 open / 1K opened)
[OK] Open file limit used: 26% (272/1K)
[OK] Table locks acquired immediately: 99% (35K immediate / 35K locks)
[!!] Connections aborted: 9%
[OK] InnoDB data size / buffer pool: 5.3M/128.0M
-------- Recommendations -----------------------------------------------------
General recommendations:
Run OPTIMIZE TABLE to defragment tables for better performance
Your applications are not closing MySQL connections properly
Variables to adjust:
query_cache_size (> 16M)

 

Co do innodb to sam nie wiem

Edytowano Sierpień 5, 2012 przez lanceq (zobacz historię edycji)

[peres.pro 9]

Odświeżam, liczę na pomoc.

[Misiek08 285]

Czemu chcesz tą bazę optymalizować? Jest z nią jakiś problem? Na pakiecie MAX w LV (jeżeli dają chociaż kawałek tego co gwarantują w CPU i RAM) to jest raczej ok.

[Gość Kamikadze]

5 ostatnich linijek - translate jak nie rozumiesz i google jak to zrobic

[Misiek08 285]

Z tym cache_size to też trzeba uważać, bo tuner może tak w nieskończoność pokazywać przy odpowiedniej bazie i zapytaniach...

 

Ogarnij może co z tym połączeniami jest nie tak.

[SanKen 63]

5 ostatnich linijek - translate jak nie rozumiesz i google jak to zrobic

 

Zacytuje text który znalazłem na pewnym forum.

 

"To po co to forum jeśli odsyłasz go do google?"

 

Udzielcie pomocy,a nie robicie wszystko by ktoś się męczył.

[Gość Kamikadze]

Udzielcie pomocy,a nie robicie wszystko by ktoś się męczył.

 

Administrator serwera powinien sam umiec znalezc problem i oraz go usunac (znalezc rozwiazanie).

 

Chcesz zeby kazdy z pierdola pisal na forum? Zaraz zrobi sie tutaj help desk osob ktore maja serwerki a nie chca placic adminowi za pierdolke

 

//sorki za brak polskich znakow ale alt mi siada...