MySql Table Optimizing
Hi, I have a table that has nearly 3 million rows in it.
Its on a MySql db.
When i query from it simply SELECT * FROM TABLE
it takes about 4-5 mins for it to return the results for me.
I am using this table within another larger query, and the time to run the query has exceeded 12 hours! which i think is far to much.
I believe its to do with this table.
I have tried to Optimize the table by de fragmenting it.
i have also tried creating another table from it (which i suppose is similar to the above)
but it still takes a long time to query it.
Can anyone suggest what i can do to help speed up performance on this table?
Its on a MySql db.
When i query from it simply SELECT * FROM TABLE
it takes about 4-5 mins for it to return the results for me.
I am using this table within another larger query, and the time to run the query has exceeded 12 hours! which i think is far to much.
I believe its to do with this table.
I have tried to Optimize the table by de fragmenting it.
i have also tried creating another table from it (which i suppose is similar to the above)
but it still takes a long time to query it.
Can anyone suggest what i can do to help speed up performance on this table?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The reason i requested both zones is because i believed the theory behind any optimization of a table would be equal in either Mysql or MSSQL, the command lines may not be exactly the same , but the logic would. And having both zones included meant i would have a better response in-case no one responded on either zone.
Please let me know if you have an issue with this acperkins
Please let me know if you have an issue with this acperkins
ASKER
Hi OP_Zaharin,
thanks for those links.
I have checked what i could on the table format.
I defragmented the table and then decided that instead of running the whole script (which is made up of 3 queries)
That i would Create 3 tables to hold each of the queries, and see how that works.
I'll let you know the progress.
thank you for the advice
thanks for those links.
I have checked what i could on the table format.
I defragmented the table and then decided that instead of running the whole script (which is made up of 3 queries)
That i would Create 3 tables to hold each of the queries, and see how that works.
I'll let you know the progress.
thank you for the advice
ASKER
Hi All, i'm hoping someone can advice me on the EXPLAIN out put, i'm trying to read this to see what it means. If anyone could clarify it would be very much appreciated.
thanks
elaine
Explain-code.csv
thanks
elaine
Explain-code.csv
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi Putoch,
- a quick explanation on the explain plan column:
http://mysql-tools.com/en/optimizing-tuning-queries/33-query-execution-plan.html
from the explain plan, the column that you might want to look into is the "type, possible_keys, key and rows"
- "type" column is the join/method use to match records from many tables. it will tell you whether it does a full table scan or not.
- "possible_keys" column indicates which indexes MySQL can choose from use to find the rows
- "key" column indicates the index that MySQL actually use. if its NULL meaning its not using any Index
- "rows" column display the number of records fetch when running each of the query step and this can tell you does your query step fetch correctly the amount of records as it should or not
- in all, EXPLAIN helps you to identify if your query is using the right approach in querying the tables involves and whether is uses the right Index or a full tablescan which usually the reason why a sql query go slow...
- a quick explanation on the explain plan column:
http://mysql-tools.com/en/optimizing-tuning-queries/33-query-execution-plan.html
from the explain plan, the column that you might want to look into is the "type, possible_keys, key and rows"
- "type" column is the join/method use to match records from many tables. it will tell you whether it does a full table scan or not.
- "possible_keys" column indicates which indexes MySQL can choose from use to find the rows
- "key" column indicates the index that MySQL actually use. if its NULL meaning its not using any Index
- "rows" column display the number of records fetch when running each of the query step and this can tell you does your query step fetch correctly the amount of records as it should or not
- in all, EXPLAIN helps you to identify if your query is using the right approach in querying the tables involves and whether is uses the right Index or a full tablescan which usually the reason why a sql query go slow...
ASKER
Thanks Guys for your help on this. I was able to understand the Explain plan in Mysql, and got some good pointers on how to optimize the db and the queries i was running, unfortunately the query was still running for hours when i tried to make some changes. thanks for all your help. Putoch
Sorry to hear that you still have an issue.
Going back to your original posting, I see you stated "I am using this table within another larger query".
I can't help wondering if you are talking about a JOIN for which we could have given you
more explicit help if we had an opportunity to see an example of the full query.
A big query involving a join that runs for hours can be made to run in seconds simply by making
sure that the fields involved in the join are indexed. Fields involved in sorting, grouping, and in
major selection should also be indexed for better performance.
Going back to your original posting, I see you stated "I am using this table within another larger query".
I can't help wondering if you are talking about a JOIN for which we could have given you
more explicit help if we had an opportunity to see an example of the full query.
A big query involving a join that runs for hours can be made to run in seconds simply by making
sure that the fields involved in the join are indexed. Fields involved in sorting, grouping, and in
major selection should also be indexed for better performance.
- try to use EXPLAIN query execution plan with your sql tool. this is to check whether your query uses INDEXES or not:
EXPLAIN EXTENDED
SELECT fieldname, fieldname
FROM tablename
WHERE fieldname = xxx
ORDER BY fieldname
LIMIT 1
\G;
- the '\G' will format the output result into a readable format.
- optimize your SQL based on the EXPLAIN result