You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2012/08/20 19:35:38 UTC

[jira] [Created] (CONNECTORS-510) MySQL database driver needs to periodically analyze and optimize

Karl Wright created CONNECTORS-510:
--------------------------------------

             Summary: MySQL database driver needs to periodically analyze and optimize
                 Key: CONNECTORS-510
                 URL: https://issues.apache.org/jira/browse/CONNECTORS-510
             Project: ManifoldCF
          Issue Type: Bug
          Components: Framework core
            Reporter: Karl Wright
            Assignee: Karl Wright


MySQL also accumulates bad statistics and dead tuples, much like PostgreSQL.  It therefore needs logic in place which re-analyzes the stats and cleans out the dead tuples.  The MySQL commands that do this are:

ANALYZE <table>
OPTIMIZE <table>

No idea how often this needs to be done yet.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CONNECTORS-510) MySQL database driver needs to periodically analyze and optimize

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CONNECTORS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438018#comment-13438018 ] 

Karl Wright commented on CONNECTORS-510:
----------------------------------------

For OPTIMIZE, MySQL has the ability to re-use freed tuples, so I expect that the number of removes/updates that need to be done before this operation is required will be fairly large (e.g. 250000 or so).

                
> MySQL database driver needs to periodically analyze and optimize
> ----------------------------------------------------------------
>
>                 Key: CONNECTORS-510
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-510
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework core
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>
> MySQL also accumulates bad statistics and dead tuples, much like PostgreSQL.  It therefore needs logic in place which re-analyzes the stats and cleans out the dead tuples.  The MySQL commands that do this are:
> ANALYZE <table>
> OPTIMIZE <table>
> No idea how often this needs to be done yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (CONNECTORS-510) MySQL database driver needs to periodically analyze and optimize

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CONNECTORS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Wright resolved CONNECTORS-510.
------------------------------------

       Resolution: Fixed
    Fix Version/s: ManifoldCF 0.7
    
> MySQL database driver needs to periodically analyze and optimize
> ----------------------------------------------------------------
>
>                 Key: CONNECTORS-510
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-510
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework core
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.7
>
>
> MySQL also accumulates bad statistics and dead tuples, much like PostgreSQL.  It therefore needs logic in place which re-analyzes the stats and cleans out the dead tuples.  The MySQL commands that do this are:
> ANALYZE <table>
> OPTIMIZE <table>
> No idea how often this needs to be done yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CONNECTORS-510) MySQL database driver needs to periodically analyze and optimize

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CONNECTORS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438402#comment-13438402 ] 

Karl Wright commented on CONNECTORS-510:
----------------------------------------

r1375365 and r1375366

                
> MySQL database driver needs to periodically analyze and optimize
> ----------------------------------------------------------------
>
>                 Key: CONNECTORS-510
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-510
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework core
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.7
>
>
> MySQL also accumulates bad statistics and dead tuples, much like PostgreSQL.  It therefore needs logic in place which re-analyzes the stats and cleans out the dead tuples.  The MySQL commands that do this are:
> ANALYZE <table>
> OPTIMIZE <table>
> No idea how often this needs to be done yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CONNECTORS-510) MySQL database driver needs to periodically analyze and optimize

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CONNECTORS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438022#comment-13438022 ] 

Karl Wright commented on CONNECTORS-510:
----------------------------------------

OPTIMIZE happens infrequently enough that it is probably comparable to VACUUM in PostgreSQL, which basically means we give this functionality to the user to set up.  Apparently, REINDEX is not needed on MySQL indexes, so that's not a problem either.  Only ANALYZE seems to be a requirement on MySQL, then.

                
> MySQL database driver needs to periodically analyze and optimize
> ----------------------------------------------------------------
>
>                 Key: CONNECTORS-510
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-510
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework core
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>
> MySQL also accumulates bad statistics and dead tuples, much like PostgreSQL.  It therefore needs logic in place which re-analyzes the stats and cleans out the dead tuples.  The MySQL commands that do this are:
> ANALYZE <table>
> OPTIMIZE <table>
> No idea how often this needs to be done yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira