On Thu, 27 Jul 2006 21:26:54 +0200
Alexander Dalloz <ad+lists@xxxxxxxxx> wrote:
> Besides the usual optimization like using best perfomance SQL statements
> and a good database layout you should take care for the [mysqld]
> key_buffer setting (/etc/my.cnf). This is RAM usage of MySQL and the
> place where the database engine tries to put as much of the indexes into
> it as possible. Ideally MySQL can get all indicies into the buffer.
> Using the STATUS variables key_read_requests and key_reads you can test
> whether the key_buffer is big enough: key_read_requests should be at
> least 100 to 1000 as big as the key_reads. It is reasonable to give the
> key_buffer 20% of the RAM you want to let MySQL use in total.
That or use heap tables or whatever are those in-ram-only short lived tables called. IIRC slashdot folks implemented them for mysql.
--
Jure Pečar
http://jure.pecar.org/
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
