Instead of your cron job, I suggest http://codenode.com/mysqlreport
The mysqlreport documentation (http://codenode.com/mysqlreportdoc)
is a pretty baseline introduction to comprehending server performance
via a mysqlreport report, and a little bit about what you can do for
certain issues.
-Daniel
Scott Haneda wrote:
>Unless I am totally off base here, the mysql docs tell very little in
>regards to how to performance tune mysql.
>
>So far I have found this article to help:
><http://www.databasejournal.com/features/mysql/article.php/10897_1402311_3>
>But it still leaves me with a ton of questions.
>
>For starters, and don't laugh, I just installed mysql and let it run,
>started adding sites to it and such. The machine has 1 gig of ram in in,
>but at times, I could ask it were a little snappier. It is a 1.2Ghz
>machine.
>
>First thing I did last night was to try to get a hnalde on this. From what
>I can tell, I have no my.cnf file in place, so there must be some default
>settings that are compiled in. I set up a cron job to run the following:
>
>show variables like 'table_cache'
>show status like 'open%_tables'
>
>I have been running this once a minute for a day now, how long should I run
>it to get an idea of what I need to change to better suit my servers load
>usage?
>
>First entry after a mysql restart:
>Wed Sep 7 03:18:00 PDT 2005
>table_cache 64
>Open_tables 64 Opened_tables 1050
>-----------
>
>Last entry as of now:
>-----------
>Wed Sep 7 16:27:01 PDT 2005
>table_cache 64
>Open_tables 64 Opened_tables 4407
>
>So it looks like Opened_tables is going to increase forever at the rate I
>have it, which I am guessing is not a good thing, but not sure what I need
>to do to fix this.
>
>I am really looking for some pretty detailed docs on exactly what I can do
>in my.cnf to make this work out better.
>
>Thanks again, and if there are any questions that would help me get a better
>answer, please let me know.
>
>
