MySQL Forums
Forum List  »  NDB clusters

Why is mysql_next_result() a required call? (was Re: Example of Cluster SLOWER than InnoDB -- help?)
Posted by: John Muehlhausen
Date: December 09, 2004 02:45PM

I'm now getting about 140m/s on my (crappy) hardware.

I save all queue operations until commit and do them all as one multiple statement query.

I'm spending about 1.7ms on each call to mysql_next_result(), which seems to indicate communication to the server for each call. Doesn't this negate the benefit of multiple statements?

If I don't call mysql_next_result() then a future query results in "Lost connection to MySQL server during query".

Is there an asynchronous API to MySQL?

Options: ReplyQuote


Subject
Views
Written By
Posted
Why is mysql_next_result() a required call? (was Re: Example of Cluster SLOWER than InnoDB -- help?)
5327
December 09, 2004 02:45PM


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.