MySQL Forums
Forum List  »  Performance

Re: Migration 4.0 to 4.1 performance problem
Posted by: Stuart McLellan
Date: October 14, 2005 07:38AM

Hi there,

I read your posting with interest as something similar has happened on my installation, upgrading from 4.0.18 to 4.1.14.

I don't want to downgrade back to 4.0 as I want to take advantage of mysqli

MySQL is run under Mac OS X server 10.3

my.cnf and mysqlreport outputs follow. The db server was restarted approx 24hrs prior to these results.

There is probably some optimisation that can be done around certain queries, however prior to the upgrade we rarely if ever had to restart the server process - the system would stay up and running, problem free for months at a time -- and max_connections was set at 60, not 100 which we have increased it to now.

If anybody has come across anything which may shed light on this, it would be greatly received.

Thanks.

# The following options will be passed to all MySQL clients
[client]
#password = your_password
port = 3306
socket = /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port = 3306
socket = /tmp/mysql.sock
tmpdir = /Volumes/ServerHD/mysql_swap/
skip-locking
key_buffer_size = 768M
max_allowed_packet = 1M
table_cache = 640
sort_buffer_size = 9M
read_buffer_size = 3M
myisam_sort_buffer_size = 64M
thread_cache_size = 16
query_cache_type=1
query_cache_size = 16M
query_cache_limit = 2M
tmp_table_size = 100M
read_rnd_buffer_size = 3M
join_buffer_size = 128M
max_join_size = 512M
max_connections = 100
old-passwords
log-slow-queries
long_query_time=12

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin

# 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

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin

# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/mysql/data/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /usr/local/mysql/data/
#innodb_log_arch_dir = /usr/local/mysql/data/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

[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

##########################################

MySQL 4.1.14-standard-l uptime 0 21:31:25 Fri Oct 14 14:35:08 2005

__ Key _________________________________________________________________
Buffer usage 116.77M of 768.00M %Used: 15.20
Write ratio 0.18
Read ratio 0.00

__ Questions ___________________________________________________________
Total 2.60M 33.54/s
Com_ 866.41k 11.18/s %Total: 33.34
COM_QUIT 866.36k 11.18/s 33.33
DMS 657.96k 8.49/s 25.32
QC Hits 208.37k 2.69/s 8.02
-Unknown 7 0.00/s 0.00
Slow 21 0.00/s 0.00 %DMS: 0.00
DMS 657.96k 8.49/s 25.32
SELECT 308.24k 3.98/s 11.86 46.85
UPDATE 289.62k 3.74/s 11.14 44.02
INSERT 49.06k 0.63/s 1.89 7.46
DELETE 11.05k 0.14/s 0.43 1.68
REPLACE 0 0.00/s 0.00 0.00
Com_ 866.41k 11.18/s 33.34
change_db 866.33k 11.18/s 33.33
show_variab 18 0.00/s 0.00
show_proces 13 0.00/s 0.00

__ SELECT and Sort _____________________________________________________
Scan 17.80k 0.23/s %SELECT: 5.78
Range 1.56k 0.02/s 0.51
Full join 6.08k 0.08/s 1.97
Range check 0 0.00/s 0.00
Full rng join 0 0.00/s 0.00
Sort scan 67.50k 0.87/s
Sort range 93.23k 1.20/s
Sort mrg pass 21 0.00/s

__ Query Cache _________________________________________________________
Memory usage 6.42M of 16.00M %Used: 40.13
Block Fragmnt 24.03%
Hits 208.37k 2.69/s
Inserts 306.94k 3.96/s
Prunes 2.38k 0.03/s
Insrt:Prune 128.70:1 3.93/s
Hit:Insert 0.68:1

__ Table Locks _________________________________________________________
Waited 6.19k 0.08/s %Total: 0.61
Immediate 1.01M 12.99/s
__ Tables ______________________________________________________________
Open 640 of 640 %Cache: 100.00
Opened 1.26k 0.02/s

__ Connections _________________________________________________________
Max used 27 of 100 %Max: 27.00
Total 866.36k 11.18/s

__ Created Temp ________________________________________________________
Disk table 29.71k 0.38/s
Table 85.27k 1.10/s
File 45 0.00/s

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Migration 4.0 to 4.1 performance problem
2064
October 14, 2005 07:38AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.