Re: Fw: Tuning MySQL for Large Database

2004-07-29 Thread Jon Drukman
matt ryan wrote: There is a perl script that comes with MySQL called mysqldumpslow. You can just run it on your slow log and it will output summary statistics about the slow log. I saw that in the docs, but I definitly dont want to install perl on a production server, I never looked to see

Fw: Tuning MySQL for Large Database

2004-07-22 Thread SGreen
I agree with Matthew. A database is a lot like a car. You can have a well-built, high-powered vehicle that could do 200mph while still carrying 15 people (good hardware + good tuning) but if you drive it off-road, alone, and in second gear (bad table structure, poor index coverage, poor SQL

Re: Fw: Tuning MySQL for Large Database

2004-07-22 Thread matt ryan
I went over your data. This is what I noticed first: | Select_full_join | 0| | Select_full_range_join | 0| | Select_range | 1| | Select_range_check | 0| | Select_scan | 301 | What command will provide this data? --

Re: Fw: Tuning MySQL for Large Database

2004-07-22 Thread SGreen
This is part of the results of a SHOW STATUS command. See one of the earlier posts for the full list of his settings. Read These For More: http://dev.mysql.com/doc/mysql/en/SHOW.html http://dev.mysql.com/doc/mysql/en/SHOW_STATUS.html

Re: Fw: Tuning MySQL for Large Database

2004-07-22 Thread matt ryan
Hmm I'm guessing my stats arent too good, lots of full table scans, but this is to be expected, my users can query any table by any column, and I cant index all column combinations Variable_name Value

Re: Fw: Tuning MySQL for Large Database

2004-07-22 Thread matt ryan
Resend, firefox did not send the way it looked when I typed it! I'm guessing my stats arent too good, lots of full table scans, but this is to be expected, my users can query any table by any column, and I cant index all column combinations Variable_name Value Select_full_join

Re: Fw: Tuning MySQL for Large Database

2004-07-22 Thread SGreen
From: http://dev.mysql.com/doc/mysql/en/Server_status_variables.html Key_reads The number of physical reads of a key block from disk. If Key_reads is big, then your key_buffer_size value is probably too small. The cache miss rate can be calculated as Key_reads/Key_read_requests.

Re: Fw: Tuning MySQL for Large Database

2004-07-22 Thread matt ryan
I've found the slow query log is useless to me, it's 50 meg right now. Is there a tool that will identify common querys? I could probably come up with some sql's if I load it into a table, but it would take quite a while to sort out. I posted a request on the mysql bugtraq to move it to a

Re: Fw: Tuning MySQL for Large Database

2004-07-22 Thread Harrison
Hi, On Thursday, July 22, 2004, at 01:42 PM, matt ryan wrote: I've found the slow query log is useless to me, it's 50 meg right now. Is there a tool that will identify common querys? I could probably come up with some sql's if I load it into a table, but it would take quite a while to sort

Re: Fw: Tuning MySQL for Large Database

2004-07-22 Thread matt ryan
There is a perl script that comes with MySQL called mysqldumpslow. You can just run it on your slow log and it will output summary statistics about the slow log. I saw that in the docs, but I definitly dont want to install perl on a production server, I never looked to see if I could do it