This is my my.cnf (copy from my-large.cnf), hope it helps you, a quick check
shows some differences:
Example mysql config file for large systems.
This is for large system with memory = 512M 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/var) 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
key_buffer = 256M
max_allowed_packet = 16M
table_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
myisam_sort_buffer_size = 64M
thread_cache = 8
query_cache_size= 16M
query_cache_type=1
Try number of CPUās*2 for thread_concurrency
thread_concurrency = 8
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 = 2
The replication master for this slave - required
#master-host =
The username the slave will use for authentication when connecting
to the master - required
#master-user =
The password the slave will authenticate with when connecting to
the master - required
#master-password =
The port the master is listening on.
optional - defaults to 3306
#master-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 = 64M
#bdb_max_lock = 100000
Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/mysql/var/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /usr/local/mysql/var/
#innodb_log_arch_dir = /usr/local/mysql/var/
You can set ā¦_buffer_pool_size up to 50 - 80 %
of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 256M
innodb_additional_mem_pool_size = 20M
Set ā¦_log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 64M
#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 = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M
[myisamchk]
key_buffer = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
<== cut here ==>
A.From: Asif Iqbal [mailto:iqbala@qwestip.net]
Sent: Wednesday, August 27, 2003 5:46 PM
To: AleŔ SuŔnik
Cc: rt-users@lists.fsck.com
Subject: RE: [rt-users] httpdās are more than 10%
My RT3 is still slow afetr upgrading it from 3.04. to 3.0.5pre3. This is how
my
cnf file looks like
[client]
port = 3306
socket = /tmp/mysql.sock
[mysqld]
port = 3306
socket = /tmp/mysql.sock
skip-locking
key_buffer = 384M
max_allowed_packet = 1M
table_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
myisam_sort_buffer_size = 64M
thread_cache = 8
query_cache_size = 32M
thread_concurrency = 8
server-id = 1
innodb_data_home_dir = /usr/local/mysql/data/
innodb_data_file_path = ibdata1:1882M;ibdata2:10M:autoextend
innodb_log_group_home_dir = /usr/local/mysql/data/
innodb_log_arch_dir = /usr/local/mysql/data/
innodb_buffer_pool_size = 384M
innodb_additional_mem_pool_size = 20M
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 = 16M
[mysql]
no-auto-rehash
[isamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M
[myisamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
I have only InnoDB and MyISAM tables as part of the default setup
Any suggestion for improvement now ?
Thanks a lot
Try optimizing your mysql (thereās plenty of info about that on the web).
You said youāve got 4gb of RAM, use it wellā¦
A.
-----Original Message-----
From: Asif Iqbal [mailto:iqbala@qwestip.net]
Sent: Saturday, August 23, 2003 11:55 PM
To: AleŔ SuŔnik
Cc: rt-users@lists.fsck.com
Subject: RE: [rt-users] httpdās are more than 10%
Try to go with my-large.cnf, the amount of RAM youāve got is plenty for
my-large.
And yes try 3.0.5pre3.
A.
using my-large instead of my-medium and upgraded from RT-3-0-4 to
RT-3-0-5pre3
and now the same ticket takes 9.5 sec to retrieve instead of 58 secs
Now I am not sure if I need to be concerned about the httpds that are
still over 10%
Thanks for all the help
-----Original Message-----
From: Asif Iqbal [mailto:iqbala@qwestip.net]
Sent: Thursday, August 21, 2003 4:46 PM
To: AleŔ SuŔnik
Subject: RE: [rt-users] httpdās are more than 10%
HW configuration?
Soalris 420R, 4x450 Mhz/4 GB Ram
mysql config?
my-medium.cnf
Tried 3.0.5pre3?
No, should I ?
A.
-----Original Message-----
From: rt-users-admin@lists.fsck.com
[mailto:rt-users-admin@lists.fsck.com]
On Behalf Of Asif Iqbal
Sent: Thursday, August 21, 2003 3:58 PM
To: rt-users@lists.fsck.com
Cc: rt-devel@lists.fsck.com
Subject: [rt-users] httpdās are more than 10%
I am using RT-3-0-4/Mysql4.0.13/Apache 1.3.27+mod_perl1/Perl 5.8
I noticed three out of 10 of my httpd sessions are taking more than
10%
of
CPU
and they are excruciatingly slow. Not sure if we need to switch to a
different
product at this time. I really had very good experience with RT2 and
not
with
RT3. I followed the instruction while upgrading to RT3.
Someone else experiencing the same way ?
Sorry I needed to vent out 
Thanks
Asif Iqbal
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x8B686E08
Thereās no place like 127.0.0.1