Hello,
I tried to optimize our server according to the hints given in the mysql manual and some articles I read. To find out whether our system needs tuning I performed what's written in the manual section 4.6.8.3:
If Key_reads is big, then your key_buffer_size variable is probably too small.
The cache miss rate can be calculated with Key_reads/Key_read_request
The rate was way to low after running the server for app. 80 days, so I doubled the key-cache and started again, controlling the ratio every 48 hours. Rate seemed to be much better (1/200 instead of 1/20 before) but from one day to the other the result dropped down on 1/4. Knowing that it can't be I controlled the absolute values and figured out, that the Key_reads-variable had an overflow reaching 4Billion. My conclusion was that the value is saved as an unsigned-int which is far to small for a long running statistic if it should be usefull longer than a couple of days.
Now my question, especially for the Mysql-developers is, if it is possible to store this values as float or another type to make the statistics usable for a longer time. Our server isn't really a big one, but the overflow happened after running the server only for 11 days.
Greetings from Germany
Lutz Maibach
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
