MySQL Forums
Forum List  »  General

Re: Finding the cause of a crashed table
Posted by: Rick James
Date: February 04, 2015 07:46PM

( innodb_buffer_pool_size / _ram ) = 16M / 4096M = 0.39% -- % of RAM used for InnoDB buffer_pool
( Innodb_pages_read / Innodb_buffer_pool_read_requests ) = 223,888 / 7010878 = 3.2% -- Read requests that had to hit disk
( Innodb_pages_written / Innodb_buffer_pool_write_requests ) = 89,477 / 395404 = 22.6% -- Write requests that had to hit disk
-- Since you have converted to InnoDB, set innodb_buffer_pool_size=1500M and key_buffer_size=20M
-- http://mysql.rjweb.org/doc.php/memory

( slow_query_log ) = OFF -- Whether to log slow queries. (5.1.12)
( long_query_time ) = 10.000000 = 10 -- Cutoff (Seconds) for defining a "slow" query.
-- Suggest ON and 2

( Uptime_since_flush_status ) = 2,042 -- How long (in seconds) since FLUSH STATUS (or server startup).
( Uptime ) = 2,042 -- How long (in seconds) the server has been running.
-- GLOBAL STATUS has not been gathered long enough to get reliable suggestions for many of the issues. Fix what you can, then come back with a new SHOW GLOBAL STATUS in a several hours.

max_connections = 600
-- Seems high.

Options: ReplyQuote


Subject
Written By
Posted
Re: Finding the cause of a crashed table
February 04, 2015 07:46PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.