Comments on: To SQL_CALC_FOUND_ROWS or not to SQL_CALC_FOUND_ROWS? http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/ Everything about MySQL Performance Thu, 28 Aug 2008 00:23:44 +0000 http://wordpress.org/?v=2.5.1 By: vlado107 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-349365 vlado107 Tue, 26 Aug 2008 21:05:26 +0000 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-349365 In first sql you are using "ORDER BY c", this column is not indexed and mysql must pass all rows to order result In first sql you are using “ORDER BY c”, this column is not indexed and mysql must pass all rows to order result

]]> By: Sunfox http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-347887 Sunfox Sat, 23 Aug 2008 07:22:58 +0000 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-347887 I have to say that COUNT(*) is faster so far. Query with LIMIT and SQL_CALC_FOUND_ROWS: 0.80 - 1.00 seconds Query without SQL_CALC_FOUND_ROWS: 0.06 seconds Added COUNT(*) query: 0.09-0.12 seconds I have to say that COUNT(*) is faster so far.

Query with LIMIT and SQL_CALC_FOUND_ROWS: 0.80 - 1.00 seconds
Query without SQL_CALC_FOUND_ROWS: 0.06 seconds
Added COUNT(*) query: 0.09-0.12 seconds

]]> By: Sergio http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-333025 Sergio Tue, 22 Jul 2008 23:40:32 +0000 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-333025 Yeap, I've tested and found that "2 query mode" (0,015 sec*) are about 10x times faster than "one with SQL_CALC_FOUND_ROWS" (0,153 sec*). The application that I've tested has 164.520 rows (42MB table). * generation time of the page where the queries were executed. That time is the minimal value which was gained after some page refreshes. Yeap, I’ve tested and found that “2 query mode” (0,015 sec*) are about 10x times faster than “one with SQL_CALC_FOUND_ROWS” (0,153 sec*).

The application that I’ve tested has 164.520 rows (42MB table).

* generation time of the page where the queries were executed. That time is the minimal value which was gained after some page refreshes.

]]> By: SQL_CALC_FOUND_ROWS - Is it faster? » Forums, Blogs, Wikis http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-312638 SQL_CALC_FOUND_ROWS - Is it faster? » Forums, Blogs, Wikis Thu, 12 Jun 2008 14:42:39 +0000 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-312638 [...] through a post on SQL_CALC_FOUND_ROWS actually being slower that running one query followed by a count query I decided I needed to do a little benchmarking on [...] [...] through a post on SQL_CALC_FOUND_ROWS actually being slower that running one query followed by a count query I decided I needed to do a little benchmarking on [...]

]]> By: techfounder » Pagination with Zend_Db_Select http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-312243 techfounder » Pagination with Zend_Db_Select Wed, 11 Jun 2008 01:02:45 +0000 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-312243 [...] in two seperate queries while the second is just one query, however it is not that obvious which one is better for performance. For our case we’ll use the first method, duplicating the original query while stripping out [...] [...] in two seperate queries while the second is just one query, however it is not that obvious which one is better for performance. For our case we’ll use the first method, duplicating the original query while stripping out [...]

]]> By: Ligio Blog » Num Rows nelle query con LIMIT http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-278873 Ligio Blog » Num Rows nelle query con LIMIT Wed, 16 Apr 2008 01:56:10 +0000 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-278873 [...] Un test dettagliato è visionabile a questo indirizzo su mysqlperformanceblog [...] [...] Un test dettagliato è visionabile a questo indirizzo su mysqlperformanceblog [...]

]]> By: SpawN » Blog Archive » MYSQL查询问题 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-259012 SpawN » Blog Archive » MYSQL查询问题 Fri, 28 Mar 2008 17:40:24 +0000 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-259012 [...] 另外从此贴中也可以分析得到，存在适当的索引在查询条件语句中，使用2个单独的查询语句要比单独使用SQL_CALC_FOUND_ROWS快的多 [...] [...] 另外从此贴中也可以分析得到，存在适当的索引在查询条件语句中，使用2个单独的查询语句要比单独使用SQL_CALC_FOUND_ROWS快的多 [...]

]]> By: Jobs Job Search Engine http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-242851 Jobs Job Search Engine Fri, 15 Feb 2008 11:44:07 +0000 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-242851 <strong>The significance of attentive job search in the human resources market.</strong> Nowadays this problem is very widespread. The agreement at present can be oral or written, and the most important conditions in them can be marked in an oral, written or mixed form. The significance of attentive job search in the human resources market.

Nowadays this problem is very widespread. The agreement at present can be oral or written, and the most important conditions in them can be marked in an oral, written or mixed form.

]]> By: techblog.tilllate.com » Comparing queries with mk-query-profiler and diff- http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-239331 techblog.tilllate.com » Comparing queries with mk-query-profiler and diff- Tue, 05 Feb 2008 16:08:53 +0000 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-239331 [...] how you do it. As an example I take the queries from this mysql performance blog article article. Because I’d like to learn what excactly SQL_CALC_FOUND_ROWS [...] [...] how you do it. As an example I take the queries from this mysql performance blog article article. Because I’d like to learn what excactly SQL_CALC_FOUND_ROWS [...]

]]> By: Колядин Алексей (donflash) » Blog Archive » Постраничная навигация и проблемы, связан http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-236081 Колядин Алексей (donflash) » Blog Archive » Постраничная навигация и проблемы, связан Wed, 30 Jan 2008 14:45:32 +0000 http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/#comment-236081 [...] чтобы понять в чём причина, пока не наткнулся на эту статью. Пересказывать её не буду, сами прочитаете, но мораль [...] [...] чтобы понять в чём причина, пока не наткнулся на эту статью. Пересказывать её не буду, сами прочитаете, но мораль [...]

]]>