Re: Up to 1 million rows Performance + Design Help
If you can't have all the items in the WHERE clause in a single index of a single table, you are probably stuck with a "filesort". Contrary to what a lot of people say, "filesort" is not the end of the world.
Run EXPLAIN to see the details for a particular query. Recommend you try different queries and different table definitions.
And, when you have enough data, be sure to turn on the slow log. The "slow" queries will be recorded, along with "rows examined". This number is a good clue of how much stuff it had to rummage through before sorting and delivering the result.
Minimizing "rows examined" is more useful than eliminating "filesort".
Subject
Written By
Posted
February 05, 2009 05:24PM
February 06, 2009 12:46AM
Re: Up to 1 million rows Performance + Design Help
May 18, 2009 11:49PM
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.