its limits?
> >
> > - Original Message - From: "Daniel" <[EMAIL PROTECTED]>
> > To: "Matthew Lenz" <[EMAIL PROTECTED]>
> > Cc: "mysql"
> > Sent: Sunday, September 11, 2005 1:12 PM
> > Subject: Re: default my.cnf
mber 11, 2005 1:12 PM
Subject: Re: default my.cnf vs huge.cnf nearly same performance with
sql-bench/run-all-tests
I think it's a common misconception that MySQL will grow to meet the
settings in my.cnf.
That is, if you have 32M of actively used indexes, there is no
difference between key_b
so the sql-bench stuff doesn't push the mysqld to its limits?
- Original Message -
From: "Daniel" <[EMAIL PROTECTED]>
To: "Matthew Lenz" <[EMAIL PROTECTED]>
Cc: "mysql"
Sent: Sunday, September 11, 2005 1:12 PM
Subject: Re: default my.cn
I think it's a common misconception that MySQL will grow to meet the
settings in my.cnf.
That is, if you have 32M of actively used indexes, there is no
difference between key_buffer = 64M
and key_buffer = 512M. Similarly, if you have a need for 128 cached
tables, you'll gain
no benefit with tabl
infact .. the default debian config (some of these are just explicit
defaults but this is what debian provides):
[mysqld]
user= mysql
pid-file= /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port= 3306
basedir = /usr
datadir
