I have a question about the prepare/execute commands provided by mysql.
I devised a benchmark, comparing updating a table using a
statement-at-a-time versus using a prepare/execute pair. The table had a
million rows.
The statement-at-a-time file looked like:
reset query cache;
update company
To hazard a guess here: the mysql console typically starts up in
autocommit mode. The neccesity of commiting after each
statement/execution could be costing you some cycles.
What is the table type of your test data? I would not expect
transactions in MyISAM would give you any beifit but under
the table is myisam, so anything having to do with transactions won't have
any effect.
On Tue, Sep 2, 2008 at 4:54 PM, Michael Dykman [EMAIL PROTECTED] wrote:
To hazard a guess here: the mysql console typically starts up in
autocommit mode. The neccesity of commiting after each
