[
https://issues.apache.org/jira/browse/IGNITE-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712584#comment-16712584
]
Pavel Kuznetsov commented on IGNITE-10329:
------------------------------------------
Since queries have been changed, updated results:
||Vendor\Benchmark (Q/sec, Avg) ||SelectBySalary ||SelectByPk
||SelectBySalaryWithJoin ||SelectByPkWithJoin||
||ignite thin inmemory |400.58 |182.69 |5,728.54 |4,619.40|
||ignite jdbc v2 inmemory |325.08 |159.80 |6,931.26 |5,403.70|
||ignite thin persistence |312.51 |136.46 |5,558.00 |4,289.53|
||ignite jdbc v2 persistence |272.12 |129.15 |6,832.41 |5,117.90|
||Mysql (tunned) |312.53 |199.77 |5,092.38 |4,356.98|
||PgSQL (tunned) |1,132.87 |75.00 |11,379.79 |10,196.34|
||Vendor\Benchmark (Q/sec, Avg) ||SelectAll ||SelectAllJoin||
||ignite thin inmemory |0.39 |0.20|
||ignite jdbc v2 inmemory |0.42 |0.19|
||ignite thin persistence |0.35 |0.16|
||ignite jdbc v2 persistence |0.37 |0.15|
||Mysql (tunned) |0.54 |0.31|
||PgSQL (tunned) |1.97 |0.99|
> Create JDBC "query" and "query join" benchmarks and compare them with
> Postgres and MySQL
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-10329
> URL: https://issues.apache.org/jira/browse/IGNITE-10329
> Project: Ignite
> Issue Type: Task
> Components: sql, yardstick
> Reporter: Vladimir Ozerov
> Assignee: Pavel Kuznetsov
> Priority: Major
> Fix For: 2.8
>
>
> Currently we have {{IgniteSqlQueryBenchmark}} and
> {{IgniteSqlQueryJoinBenchmark}} benchmarks which query data over salary range
> and optionally joins it with second table. Let's create a set of similar
> benchmarks which will use JDBC to load and query data, and execute them
> against one-node Ignite cluster, MySQL and Postgres.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
