You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Stanilovsky Evgeny (Jira)" <ji...@apache.org> on 2020/07/14 12:38:00 UTC

[jira] [Commented] (IGNITE-13255) ODBC/JDBC is very slow

    [ https://issues.apache.org/jira/browse/IGNITE-13255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157335#comment-17157335 ] 

Stanilovsky Evgeny commented on IGNITE-13255:
---------------------------------------------

may be it would be helpful somehow, we compare odbc\jdbc performance here [1]

[1]https://issues.apache.org/jira/browse/IGNITE-12374

> ODBC/JDBC is very slow
> ----------------------
>
>                 Key: IGNITE-13255
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13255
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc, odbc
>    Affects Versions: 2.8.1
>            Reporter: Christian Ehrlicher
>            Priority: Major
>         Attachments: create_table.sql, drop_table.sql
>
>
> The ODBC/JDBC interface seems to be very slow compared to other databases. I'm not sure if it is a configuration problem on my side but since I more or less used the default configuration I don't think so.
> Attached a small testcase which simply creates 100 tables and another one which deletes them afterwards. Executing both in a sql browser (I'm using DBeaver for this test, but should not matter) takes 17 and 20 seconds and java.exe takes ~2 full cpus. Executing this on a postgreSQL or informix database the runtime is ~200 / 60 msec.
> Even considering that it's no sql database I find the execution times far from useable. Is this maybe a regression?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)