MySQL Forums
Forum List  »  Connector/ODBC

Connector/ODBC FP conversion overhead
Posted by: David Yeowart
Date: August 11, 2014 07:20PM

We currently have a C++ application that reads significant amounts of primarily float point data from several potential data sources - MySQL included. As maintaining multiple database layers is getting problematic we're investigating dropping all but the ODBC driver, but we're having issues with Connector/ODBC performance (almost an order of magnitude slower than libmysql - and given this is the primary database we use, that's a problem).

Profiling reveals this is because data appears to be serialised to string for transmission then converted back to a binary format on the client instead of using a binary protocol (compared to the native library a nontrivial chunk of our runtime ends up being in strtold, which is being called by sql_get_data). Checking the source confirms this. While that probably doesn't matter much for most applications, it's quite problematic here - is this intended behaviour? Have we missed a flag for a more appropriate transport mechanism?

Options: ReplyQuote


Subject
Written By
Posted
Connector/ODBC FP conversion overhead
August 11, 2014 07:20PM


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.