8 messages in com.mysql.lists.dotnetRe: mysql driver speed
FromSent OnAttachments
Lance Johnson01 Feb 2005 07:45 
Jordan Sparks01 Feb 2005 08:49 
Bob Dankert01 Feb 2005 08:56 
Lance Johnson01 Feb 2005 09:14 
Jorge Bastos01 Feb 2005 11:03 
Jorge Bastos01 Feb 2005 11:09 
Frank01 Feb 2005 14:15 
Barry Zubel02 Feb 2005 00:36 
Subject:Re: mysql driver speed
From:Jorge Bastos (mysq@decimal.pt)
Date:02/01/2005 11:09:11 AM
List:com.mysql.lists.dotnet

Well that's strange, i changed from 0.76 old bytefx to 1.0.4 and noticed no diference in speed. There're some issues or bugs in a version 0.75beta or something, but with thing i notice nothing.

----- Original Message ----- From: "Scott Underwood" <sco@firelan.net> To: "Jorge Bastos" <mysq@decimal.pt> Sent: Tuesday, February 01, 2005 7:00 PM Subject: RE: mysql driver speed

Why? I've used the 1.x versions of the connector and constantly keep going back to the .76 version of the ByteFx connector. The reason is simply speed of the connector. Since the MySQL version came out the query retrieval speed has been much slower than the ByteFx version was. As for ODBC it has a reliable .NET interface that will allow connection to the database. I admit ODBC is old, but what makes it a worst solution?

Going to ODBC is like... going to the past.

----- Original Message ----- From: "Lance Johnson" <ljoh@DOCS.com> To: <dot@lists.mysql.com> Sent: Tuesday, February 01, 2005 5:15 PM Subject: RE: mysql driver speed

Your comment on the timing issue is what my thoughts are. On the odbc driver my results from dotnet show either it's taking 0seconds or right at .015seconds. For the mysql direct driver one, it's taking on average .15 seconds. It ranges from .12 seconds up to .20 seconds. But the fact of the matter is it's showing over .1 seconds.

For now we're switching back to odbc because this speed difference is huge when you perform a lot of queries. When just performing queries every now and then, it's not a big deal.

-----Original Message----- From: Bob Dankert [mailto:bo@nvsn-it.com] Sent: Tuesday, February 01, 2005 10:57 AM To: dot@lists.mysql.com Subject: RE: mysql driver speed

There are HIGHLY accurate counters available, you just need to use P/Invoke with the API to access them.

More information can be found here:

http://support.microsoft.com/kb/306979/EN-US/

Showing a 10x speed difference with standard timing should be rather accurate as well, especially if it is consistently reproducible.

Mine's blazing fast. But also remember that those numbers aren't all that accurate. Computers do a lousy job a giving accurate subsecond timing. Do you have any try-catch statements that could be slowing things down?

Has anybody noticed slow performance or is it just me? I can do a simple query to a mysql db on our network and it's taking on average .15 seconds. With the mysql odbc driver it's taking .015 seconds. That's a factor of 10. Something doesn't seem right to me.