MySQL Forums
Forum List  »  Performance

Re: Mysql seems to be bogged down
Posted by: Mike Martinez
Date: September 12, 2005 11:31AM

Hi AF,
No, I've had no luck with tracking down the cause of this problem. All I can say from this point is it's got something to do with mysql and the way it's running or maybe the way it's archiving data (cache). I really have no idea.
I spoke the gentleman who originally set-up this server before I arrived and he suggested the problem was do to the age of the OS (SunOS 5.9), Apache (1.3.29) and mysql (3.23.49). He even went as far to suggest that I update the OS to SunOs 10.
I really don't know what to say about this (performance - speed of my server bogged down by MySql [maybe]). I'm sure this has to do with some setting in the config file for MySql (my.cnf) which I've included for anyones review and suggestion.

Thanks for all your help
Mike

-----------------------------------------------------------------------------------------------
# Example mysql config file for very large systems.
#
# This is for large system with memory of 1G-2G where the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# One can in this file use all long options that the program supports.
# If you want to know which options a program support, run the program
# with --help option.

# 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
skip-locking
skip-external-locking
key_buffer = 684M
max_allowed_packet = 5M
table_cache = 5512
sort_buffer_size = 50M
read_buffer_size = 50M
myisam_sort_buffer_size = 228M
max_sort_length=5024
thread_cache = 24
query_cache_size = 80M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 4
skip_innodb
max_connections=200
join_buffer_size=50M
max_allowed_packet=1048576
max_delayed_threads=100
max_heap_table_size=56777216
tmp_table_size=100M
log
#low_priority_updates=0
max_write_lock_count=500M
# 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 = 384M
#bdb_max_lock = 100000

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/mysql/data/
#innodb_data_file_path = ibdata1:2000M;ibdata2: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 = 384M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 100M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 64M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 600M
sort_buffer_size = 600M
read_buffer = 10M
write_buffer = 10M

[myisamchk]
key_buffer = 600M
sort_buffer_size = 600M
read_buffer = 10M
write_buffer = 10M

[mysqlhotcopy]
interactive-timeout

Options: ReplyQuote


Subject
Views
Written By
Posted
2348
September 09, 2005 12:40PM
1454
A F
September 09, 2005 01:45PM
1693
September 09, 2005 09:32PM
1498
A F
September 12, 2005 07:50AM
Re: Mysql seems to be bogged down
2011
September 12, 2005 11:31AM
1355
September 12, 2005 05:13PM
1340
September 16, 2005 05:28PM
1515
September 20, 2005 09:54AM
1541
September 22, 2005 04:14PM


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.