#30194 [Opn->Bgs]: Mysqli Prepared Statements work very slow when CLOB\BLOB is in result set
ID: 30194
Updated by: georg@php.net
Reported By: phoeniks2k at mail dot ru
-Status: Open
+Status: Bogus
-Bug Type: Performance problem
+Bug Type: MySQLi related
Operating System: All
PHP Version: 5.0.1
New Comment:
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php
Retrieving only a single recordset with a prepared
statement is of course slower. Why do you use
mysqli_stmt_store_result? The first recordset is already
sent to client after mysqli_stmt_execute.
Also there is no reproducible testcase in your bug report.
Previous Comments:
------------------------------------------------------------------------
[2004-09-22 14:38:07] phoeniks2k at mail dot ru
Sorry, some additional info:
Mysql 4.1.4 Gamma and clobs are not empty
------------------------------------------------------------------------
[2004-09-22 14:27:20] phoeniks2k at mail dot ru
Description:
------------
If result set has clob\blob fields, retrieving data is VERY slow.
Query "SELECT SQL_NO_CACHE id, xml_clob FROM some_table WHERE id = 1"
executes 1000 times for about 0.4 seconds on my server;
But this query rewriten with statement execs 20 time for 6(!)
seconds!!!
Every time i call:
exec, store result, fetch, free_result
P.S. SQL_NO_CACHE is used for clean noncached result times
Expected result:
----------------
STMT performance higher then normal query performance
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=30194&edit=1
Thread (8 messages)