Re: poor performance on good hardware
Posted by:
Rick James
Date: December 10, 2009 10:39PM
Data_length: 1327497216
Max_data_length: 0
Index_length: 1492910080
Data_free: 64293437440
64GB - 1.3GB - 1.4 GB = 61GB.
file_per_table might have some overhead -- Assuming 8MB increment in allocating, and 150 tables, that adds up to 600MB+ of wasted space (8*150/2). But that seems trivial compared to the amount of disk you seem to have.
Alas, there is no standard slowlog rotation. Here are some ways:
Plan A:
1. stop mysqld
2. mv the slowlog
3. start mysqld
Plan B (not sure if it works):
1. mv the slowlog
2. FLUSH LOGS;
Note: In Unix, mv is just a rename. The FLUSH may cause it to close and reopen the file, thereby discovering that it now does not exist.
Subject
Views
Written By
Posted
3659
December 02, 2009 08:36AM
2013
December 02, 2009 10:13PM
1797
December 03, 2009 02:17AM
1742
December 03, 2009 02:18AM
2320
December 08, 2009 03:42AM
1700
December 08, 2009 08:30PM
2878
December 09, 2009 05:42AM
2119
December 09, 2009 08:28PM
1898
December 10, 2009 11:10AM
Re: poor performance on good hardware
1888
December 10, 2009 10:39PM
1848
December 11, 2009 10:43AM
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.