From aa99ee9826e628c1b106c22f376326d6dd8b0fde Mon Sep 17 00:00:00 2001 From: mh Date: Thu, 7 Aug 2008 09:24:59 +0000 Subject: merged with puzzle --- files/backup/mysql_backup.cron | 2 +- files/config/my.cnf.CentOS | 38 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 39 insertions(+), 1 deletion(-) (limited to 'files') diff --git a/files/backup/mysql_backup.cron b/files/backup/mysql_backup.cron index 388f8ea..a9bb24a 100644 --- a/files/backup/mysql_backup.cron +++ b/files/backup/mysql_backup.cron @@ -1 +1 @@ -00 01 * * * root /usr/bin/mysqldump --all-databases --all | gzip > /var/lib/mysql/data/mysqldump.sql.gz && chmod 600 /var/lib/mysql/data/mysqldump.sql.gz +00 01 * * * root /usr/bin/mysqldump --default-character-set=utf8 --all-databases --all | gzip > /var/lib/mysql/data/mysqldump.sql.gz && chmod 600 /var/lib/mysql/data/mysqldump.sql.gz diff --git a/files/config/my.cnf.CentOS b/files/config/my.cnf.CentOS index ba06d59..1182b2e 100644 --- a/files/config/my.cnf.CentOS +++ b/files/config/my.cnf.CentOS @@ -8,7 +8,45 @@ socket=/var/lib/mysql/mysql.sock old_passwords=0 bind-address=127.0.0.1 + +skip-bdb + +# Query cache is used to cache SELECT results and later return them +# without actual executing the same query once again. Having the query +# cache enabled may result in significant speed improvements, if your +# have a lot of identical queries and rarely changing tables. See the +# "Qcache_lowmem_prunes" status variable to check if the current value +# is high enough for your load. +# Note: In case your tables change very often or if your queries are +# textually different every time, the query cache may result in a +# slowdown instead of a performance improvement. +query_cache_size = 64M + +# Log slow queries. Slow queries are queries which take more than the +# amount of time defined in "long_query_time" or which do not use +# indexes well, if log_long_format is enabled. It is normally good idea +# to have this turned on if you frequently add new queries to the +# system. +log_slow_queries + +# How many threads we should keep in a cache for reuse. When a client +# disconnects, the client's threads are put in the cache if there aren't +# more than thread_cache_size threads from before. This greatly reduces +# the amount of thread creations needed if you have a lot of new +# connections. (Normally this doesn't give a notable performance +# improvement if you have a good thread implementation.) +thread_cache_size = 4 +# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and +# row data. The bigger you set this the less disk I/O is needed to +# access data in tables. On a dedicated database server you may set this +# parameter up to 80% of the machine physical memory size. Do not set it +# too large, though, because competition of the physical memory may +# cause paging in the operating system. Note that on 32bit systems you +# might be limited to 2-3.5G of user level memory per process, so do not +# set it too high. +innodb_buffer_pool_size = 50MB + [mysql.server] user=mysql basedir=/usr -- cgit v1.2.3