[
https://issues.apache.org/jira/browse/IGNITE-13255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158899#comment-17158899
]
Christian Ehrlicher commented on IGNITE-13255:
----------------------------------------------
I did some more testing. Looks like it's getting slower the more tables are in.
Adding the first 100 takes 17 seconds, the next 100 already take 29 seconds and
then it's already 43 seconds. Dropping is worse: 300 > 200 takes 82seconds and
4 cpus, 200-> 100 50seconds, 100 -> 0 20 sceonds)
Since the odbc/jdbc driver does not seem to support schemas (according to
[https://apacheignite-sql.readme.io/docs/ddl] ) we have to put a lot of tables
into one schema so this is really a showstopper for us :(
> 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)
