ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taras Ledkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6217) Add benchmark to compare JDBC drivers and native SQL execution
Date Mon, 23 Oct 2017 08:24:00 GMT

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

Taras Ledkov commented on IGNITE-6217:
--------------------------------------

Finally, I added the benchmark configurations: 
- {{benchmark-jdbcv2-sql.properties}} for JDBC v2 client and native SQL (1 server, 1 client);
- {{benchmark-jdbc-thin.properties}} for JDBC thin client (1 server, 1 ignite client, 1 jdbc
client is connected with ignite client). 
The driver is configured with 4 executor threads.

We have to create different configurations because *yardstick* framework doesn't support different
sets of hosts into one configuration.

|| Benchmark || Ops /sec (1 row) ||  Ops/sec (1000 rows) || Ops / sec (1M rows) ||
| Nativa SQL | 28187.87 | 2681.98 |  2.22 |
| JDBC v2 | 23914.44 ({color:#d04437}-15%{color}) | 2348.59 ({color:#d04437}-12%{color}) |
2.19 ({color:#d04437}-1%{color}) |
| JDBC thin | 13856.23 ({color:#d04437}-51%{color}) | 2277.57 ({color:#d04437}-15%{color})
| 2.17 ({color:#d04437}-2%{color}) |



> Add benchmark to compare JDBC drivers and native SQL execution
> --------------------------------------------------------------
>
>                 Key: IGNITE-6217
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6217
>             Project: Ignite
>          Issue Type: Task
>          Components: jdbc, sql, yardstick
>    Affects Versions: 2.1
>            Reporter: Taras Ledkov
>            Assignee: Taras Ledkov
>             Fix For: 2.4
>
>
> We have to compare performance of the native SQL execution (via Ignite SQL API), JDBC
v2 driver, that uses Ignite client to connect to grid and JDBC thin client.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message