Larry Hotchkiss wrote:
>
> In the manual, it states "if Key_reads is big, then your key_cahce is
> probably too small."....so what exactly is BIG???
>
Its all about ratios, you just want a hit cache hit, so that
your read_requests are a lot larger than your actual reads.
| Key_read_requests | 6324 |
| Key_reads | 51 |
100 - 1 ratio is OK. 1000 - 1 would be better. Obvi, this database hasn't
been up very long, but this ratio should only improve over time if the
key buffer is large enough.
> Same thing for opened_tables, it states "if opened_tables is big then your
> then your table_cache variable is probably too small". Can someone please
> define BIG????
>
| Open_tables | 19 |
| Opened_tables | 851 |
This is big, especially for the amount of action my db has seen.
BUT, I call [flush tables] all the time, so that my data gets
written to disk in a more persistent way ( I'm on NT, which doesn't
play as nice as Linux ). You might want to see if your flush-time
is set to anything, as this could be a source of closing your table,
which might be a good thing anyway now and then.
You probably should have your open_tables and opened_tables
be in the same area if you haven't been running your database for
very long ( < 1 day ).
--Josh
_________________________________________________________________
Joshua Chamas Chamas Enterprises Inc.
NodeWorks >> free web link monitoring Huntington Beach, CA USA
http://www.nodeworks.com 1-714-625-4051
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
