If things were that easy, there probably wouldn't be a DBA job title.
Tuning a database requires knowledge of the data, how it is accessed and what variables will affect those access patterns. There are some basic formulas for speeding up a typical database with typical access patterns.
If you only have 256MB on the machine, I would say you need to upgrade. RAM is fairly cheap and it's probably the most important hardware piece.
I've read a few select chapters of "High Performance MySQL" which I have found very interesting.
First and foremost is good database design. I don't know what you are tracking, but 2,700+ tables seems like an awful lot for just about any design. If you are accessing all those tables, that's a lot of file handles for the OS to have open and your cache is probably thrashing.
On May 19, 2005, at 9:01 PM, Stephen More wrote:
Is there a good place/book to lookup formulas for tunning mysql ?
What size should the table_cache be ? I have 2,770 tables....
What size should the key_buffer be ? I am only using 38 MB out of 265 MB, yet my Index Length reported by mysql-administrator is 2.72 G
Total number of records are 61 Million Rows. Most queries will be select on primary key, or group by primary key.
Any help is appreciated. -Steve More
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- Brent Baisley Systems Architect Landover Associates, Inc. Search & Advisory Services for Advanced Technology Environments p: 212.759.6400/800.759.0577
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
