[wp-trac] [WordPress Trac] #10469: use of SQL_CALC_FOUND_ROWS needs to be eliminated

[WordPress Trac]

#10469: use of SQL_CALC_FOUND_ROWS needs to be eliminated
--------------------------+-------------------------------------------------
 Reporter:  _ck_          |       Owner:  ryan        
     Type:  defect (bug)  |      Status:  new         
 Priority:  normal        |   Milestone:  2.9         
Component:  Query         |     Version:  2.9         
 Severity:  normal        |    Keywords:  dev-feedback
--------------------------+-------------------------------------------------
Changes (by dd32):

  * keywords:  => dev-feedback
  * version:  => 2.9
  * milestone:  Unassigned => 2.9


Comment:

 I think some investigating+profiling is needed of the WordPress SQL
 queries, SQL_CALC_FOUND_ROWS may be faster than COUNT() on some queries,
 and vice versa, but they need to be applied direectly to the WordPress
 generated queries as well.

 Also, While that example doesnt include any joins or complexities, The
 Query API can easily generate something with taxonomy joins (categories)
 or added clauses(archives) or joins (Meta tables) or a combination.. IMO
 it should be optimized for the most common use-cases and the least-
 performing cases should potentially look for alternate methods perhaps?

 Milestone: Future Release for long-standing "low priotity" defects,
 Current-trunk for all other defects, point release back-porting at
 commiters discretion. (Generic reply for when I change the
 milestone)[[BR]]
 Component: Tempted to change to Performance/Optimization as well, Not
 really a Query "bug" as such..

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/10469#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software