long query

mahdy_sharifi

• January 20, 2015 15:58

Hello I see following query cause too long query time even over 200 sec
localhost | information_schema | Query | 127 | Opening tables | SELECT data_free FROM tables WHERE ENGINE = 'InnoDB'
Is this munin related database ? Regards

• 

  cPanelMichael

  • January 21, 2015 13:06

  Hello :) This is likely stems from the following option that's configured in "Tweak Settings" under the "SQL" tab: Use INFORMATION_SCHEMA to acquire MySQL" disk usage Per it's description: Using INFORMATION_SCHEMA ensures that disk usage by MySQL tables is included in totals. However, enabling this option may cause a significant drop in performance as MySQL may become unresponsive until data collection is complete. Disabling this option causes the system to query the filesystem directly, potentially excluding disk space used by some database tables. Note: If you use a remote MySQL server, you must turn this setting On in order to calculate MySQL disk usage. You may want to disable this option to see if it helps improve performance. Thank you.

  0
• 

  mahdy_sharifi

  • January 29, 2015 08:42

  Not resolved yet . # Time: 150129 12:25:25 # User@Host: root[root] @ localhost [] # Query_time: 12.492698 Lock_time: 0.000093 Rows_sent: 1 Rows_examined: 88805 use information_schema; SET timestamp=1422521725; SELECT count(*) FROM tables WHERE ENGINE = 'InnoDB';
  

  0
• 

  cPanelMichael

  • January 29, 2015 17:46

  To clarify, are you still experiencing issues after disabling the "Use INFORMATION_SCHEMA to acquire MySQL" disk usage" option on your server? Thank you.

  0
• 

  mahdy_sharifi

  • January 29, 2015 21:34

  ]To clarify, are you still experiencing issues after disabling the "Use INFORMATION_SCHEMA to acquire MySQL" disk usage" option on your server? Thank you.

  
  yes ... problem exist after disabling .

  0
• 

  cPanelMichael

  • January 30, 2015 15:52

  This is likely an unsupported issue, but feel free to open a support ticket using the link in my signature so we can verify it's not caused by any cPanel configuration settings. You can post the ticket number here so we can update this thread with the outcome. Thank you.

  0

Please sign in to leave a comment.