P
postcd
Mysql says in phpmyadmin stats:
Quote:
Key reads:
889.7 k
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.
It is just few minutes after mysql restart.
There is mentioned key buffer size, but when i add the size recommended by MysqlTuner1.3 (3.5G) mysql wont start saying "Timeout error occurred trying to start MySQL Daemon."
Code:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 157G 52G 105G 33% /
/dev/simfs 157G 52G 105G 33% /var/named/chroot/var/run/dbus
there is mysql db file in /var/lib/mysql... which has 14Gb
so im unsure how to solve this issue and add keybuffer - if its wise
Continue reading...
Quote:
Key reads:
889.7 k
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.
It is just few minutes after mysql restart.
There is mentioned key buffer size, but when i add the size recommended by MysqlTuner1.3 (3.5G) mysql wont start saying "Timeout error occurred trying to start MySQL Daemon."
Code:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 157G 52G 105G 33% /
/dev/simfs 157G 52G 105G 33% /var/named/chroot/var/run/dbus
there is mysql db file in /var/lib/mysql... which has 14Gb
so im unsure how to solve this issue and add keybuffer - if its wise
Continue reading...