If you have previously enabled ODBC Tracing, having that set can slow you down by this much (and often even more so). Disabling that can be done from the ODBC Administrator (ODBCAD32.exe).
If running on Unix/Linux tracing is enabled in the .odbc.ini usually (if using a 3rd party driver manager may also do tracing in it's own way).
I do not expect this to be due to a bug (at least not yet and not in the driver). Normally the ODBC driver that comes with SQL Anywhere is very efficient.
But do be careful when comparing performance with different APIs. Often such quick tests reveal more about the performance of the different applications than the API.
You can always develope any application to be generic and make no assumptions about the specific schema or back end RDBMs; which usually means slower performance due to the need to make many more API calls to accomplish the same functionality.
One warning, many of the SQL Anywhere drivers can take an ODBC DSN as a connection parameter but doing so does not always mean you are going through the ODBC API. The DSN may just represent registry (or .odbc.ini) connection as a common repository that other drivers for other APIs can utilize as a common repository. Our JDBC, Ole/DB and .Net data adapter drivers can all do that as can Embedded SQL ... but that does not mean the ODBC driver or the ODBC driver manager are involved.
If you need more help you might want to provide more details about the comparison's you are doing, execution enviornments etc . . .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.