[ODBC-120] slow performance on querys with large number of result rows Created: 2017-11-13 Updated: 2021-03-05 Resolved: 2018-11-04 |
|
| Status: | Closed |
| Project: | MariaDB Connector/ODBC |
| Component/s: | General |
| Affects Version/s: | 3.0.2 |
| Fix Version/s: | 2.0.16, 3.0.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | David Thompson (Inactive) | Assignee: | Lawrin Novitsky |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
centos7 with ColumnStore 1.1 or Server 10.2.9 |
||
| Attachments: |
|
| Description |
|
There appears to be a significant overhead in query and returning results when using ODBC. I can reproduce this on both windows and unix but using unix here. Create the following orders table:
test data attached gzipped In my case using a separate VM as the ODBC client host. Using isql piped to /dev/null:
using same with mysql odbc:
with mysql client:
I can understand some overhead of ODBC but ours seem large and is not as good as mysql community driver performance? Config:
|
| Comments |
| Comment by Lawrin Novitsky [ 2017-11-19 ] |
|
I found the cause, and have tentative fix. However, it breaks some functionality(some testcases fail). Thus it will take some more time |
| Comment by Lawrin Novitsky [ 2017-11-23 ] |
|
The fix has been pushed to odbc-3.0 branch. |
| Comment by David Thompson (Inactive) [ 2017-11-28 ] |
|
The fix on average looks good to me, certainly addresses the massive discrepency. More specifically on dbt3/tpch orders table with 50k rows the mariadb driver is faster than mysqls. With a wider table (the lending club data) we are slight slower but in the same ballpark. |
| Comment by Lawrin Novitsky [ 2018-11-04 ] |
|
I have opened separate ticket( |