Kezdőlap › Fórumok › Debiannal kapcsolatos kérdések › sql tulterheltség
- This topic has 30 hozzászólás, 6 résztvevő, and was last updated 18 years telt el by
mesti.
-
SzerzőBejegyzés
-
2007-06-06-18:11 #2114265
talán
2007-06-06-18:11 #2114266talán
2007-06-06-18:14 #2114267feltöltöm a configokat szétnéztek benne?
2007-06-06-18:14 #2114268feltöltöm a configokat szétnéztek benne?
2007-06-08-19:20 #2114269Code:#
# 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]
old_passwords = true
# We activated the above for connections from hosts running Debian Woody/Sarge!
#
# Prior to MySQL 5.0, user passwords were stored in a rather weak way. This
# has been improved with the drawback that client programs shipped with
# Debian Woody/Sarge (technically: linked against libmysqlclient.so.12 or
# earlier) cannot connect any more if either their account has either been
# created or their password has been modified using MySQL 5.0.
# See http://dev.mysql.com/doc/refman/5.0/en/old-client.html
#
# * 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
language = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking you can now listen only on
# localhost which is more compatible and is not less secure.
# bind-address = 127.0.0.1
skip-networking
#
# * Fine Tuning
#
key_buffer = 600M
max_allowed_packet = 600M
thread_stack = 5000K
thread_cache_size = 11
#
# * Query Cache Configuration
#
query_cache_limit = 49748576
query_cache_size = 499777216
query_cache_type = 1
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement 🙂
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#
# The following can be used as easy to replay backup logs or for replication.
#server-id = 1
log_bin = /var/log/mysql/mysql-bin.log
# WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!
expire_logs_days = 11
max_binlog_size = 999M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * BerkeleyDB
#
# According to an MySQL employee the use of BerkeleyDB is now discouraged
# and support for it will probably cease in the next versions.
skip-bdb
#
# * 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!
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
#skip-innodb
#
# * 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 = 600M[mysql]
#no-auto-rehash # faster start of mysql but no tab completition[isamchk]
key_buffer = 600M#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the ndbd storage daemons,
# not from the ndb_mgmd management daemon.
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1már pár dolgot átirtam kicsit jobb de még mosse tökéletes mi lehet a gond ebben a configban????????????
2007-06-08-19:20 #2114270Code:#
# 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]
old_passwords = true
# We activated the above for connections from hosts running Debian Woody/Sarge!
#
# Prior to MySQL 5.0, user passwords were stored in a rather weak way. This
# has been improved with the drawback that client programs shipped with
# Debian Woody/Sarge (technically: linked against libmysqlclient.so.12 or
# earlier) cannot connect any more if either their account has either been
# created or their password has been modified using MySQL 5.0.
# See http://dev.mysql.com/doc/refman/5.0/en/old-client.html
#
# * 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
language = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking you can now listen only on
# localhost which is more compatible and is not less secure.
# bind-address = 127.0.0.1
skip-networking
#
# * Fine Tuning
#
key_buffer = 600M
max_allowed_packet = 600M
thread_stack = 5000K
thread_cache_size = 11
#
# * Query Cache Configuration
#
query_cache_limit = 49748576
query_cache_size = 499777216
query_cache_type = 1
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement 🙂
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#
# The following can be used as easy to replay backup logs or for replication.
#server-id = 1
log_bin = /var/log/mysql/mysql-bin.log
# WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!
expire_logs_days = 11
max_binlog_size = 999M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * BerkeleyDB
#
# According to an MySQL employee the use of BerkeleyDB is now discouraged
# and support for it will probably cease in the next versions.
skip-bdb
#
# * 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!
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
#skip-innodb
#
# * 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 = 600M[mysql]
#no-auto-rehash # faster start of mysql but no tab completition[isamchk]
key_buffer = 600M#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the ndbd storage daemons,
# not from the ndb_mgmd management daemon.
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1már pár dolgot átirtam kicsit jobb de még mosse tökéletes mi lehet a gond ebben a configban????????????
2007-06-08-22:03 #2114271mesti wrote:feltöltöm a configokat szétnéztek benne?Rég nem vigyorogtam ennyit. Lassú az autóm, megmondom a csomagtartó méretét, mi lehet a baj? Kb. ezt írtad. Még azt sem lehet megmondani, hogy az általad csatolt konfig hatékony-e (a szerver infói nélkül). Ugyanis csak az adatbázis „vasra feszítését” írja le a konfig, mást nem. Amit keresel, az az adattáblák definíciója (konkrétan: indexelés, nézetek).
Így tutod megnézni:
$ mysqldump –all-databases –create-options –no-data
Persze nem árt az SQL nyelvet ismerni.
2007-06-08-22:03 #2114272mesti wrote:feltöltöm a configokat szétnéztek benne?Rég nem vigyorogtam ennyit. Lassú az autóm, megmondom a csomagtartó méretét, mi lehet a baj? Kb. ezt írtad. Még azt sem lehet megmondani, hogy az általad csatolt konfig hatékony-e (a szerver infói nélkül). Ugyanis csak az adatbázis „vasra feszítését” írja le a konfig, mást nem. Amit keresel, az az adattáblák definíciója (konkrétan: indexelés, nézetek).
Így tutod megnézni:
$ mysqldump –all-databases –create-options –no-data
Persze nem árt az SQL nyelvet ismerni.
2007-06-08-23:04 #2114273Valahol láttam egy jó kis diskurzust arról, hogy ki hogyan konfigolja a Mysql-t. Számos variáció mellett leginkább erős vassal gyors winchesterrel és sok rammal lehet a legjobb eredményt elérni
http://forum.mysqlperformanceblog.com/s/m/1292/2007-06-08-23:04 #2114274Valahol láttam egy jó kis diskurzust arról, hogy ki hogyan konfigolja a Mysql-t. Számos variáció mellett leginkább erős vassal gyors winchesterrel és sok rammal lehet a legjobb eredményt elérni
http://forum.mysqlperformanceblog.com/s/m/1292/ -
SzerzőBejegyzés
- Be kell jelentkezni a hozzászóláshoz.
legutóbbi hsz