server optimization, can this harm before i do it?

erinys

New member
Joined
Mar 7, 2008
Messages
3
hi guys.

the people at VB gave the following (only step 1) for mysql optimization.
is it good info? in other words can i do that without problems?

1. Upgrade MySQL 5.0.45 or 5.0.51
2. Edit mysql server's /etc/my.cnf

[mysqld]
safe-show-database
#old_passwords
back_log = 50
skip-innodb
max_connections = 500
key_buffer_size = 64M
myisam_sort_buffer_size = 64M
join_buffer_size = 1M
read_buffer_size = 1M
sort_buffer_size = 2M
table_cache = 4000
thread_cache_size = 256
wait_timeout = 90
connect_timeout = 10
tmp_table_size = 64M
max_heap_table_size = 64M
max_allowed_packet = 64M
net_buffer_length = 16384
max_connect_errors = 10
thread_concurrency = 4
concurrent_insert = 2
table_lock_wait_timeout = 30
read_rnd_buffer_size = 786432
bulk_insert_buffer_size = 8M
query_cache_limit = 4M
query_cache_size = 64M
query_cache_type = 1
query_prealloc_size = 262144
query_alloc_block_size = 65536
transaction_alloc_block_size = 8192
transaction_prealloc_size = 4096
default-storage-engine = MyISAM
max_write_lock_count = 16
collation-server=latin1_general_ci

[mysql.server]
user=mysql

[mysqld_safe]
err-log=/var/log/mysqld.log
pid-file=/var/lib/mysql/mysql.pid
nice = -5
open_files_limit = 8192

[mysqldump]
quick
max_allowed_packet = 16M

[myisamchk]
key_buffer = 64M
sort_buffer = 64M
read_buffer = 16M
write_buffer = 16M
 
the upgrade of mysqld - unlikely its considered standard practice to keep up to date.

the my.cnf, you can try it, if its problamatic just revert it.
 
Everything depends on your MySQL usage. It is impossible to give certain advices without it and you will be unable to optimize your server in this way.
 
Back
Top