[
https://issues.apache.org/jira/browse/IGNITE-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721442#comment-16721442
]
Pavel Kuznetsov commented on IGNITE-10329:
------------------------------------------
Results for the run on one single host:
||Vendor\Benchmark (Q/sec, Avg) ||SelectBySalary
||SelectBySalaryWithJoin ||SelectByPk ||SelectByPkWithJoin||
||ignite thin inmemory |432.43 |187.75 |8,020.02 |5,960.67|
||ignite jdbc v2 inmemory |324.98 |152.37 |8,084.45 |6,018.40|
||ignite thin persistence |336.52 |135.92 |7,761.49 |5,548.79|
||ignite jdbc v2 persistence |271.41 |121.25 |8,100.08 |5,664.68|
||Mysql (tunned) |328.34 |203.46 |5,988.74 |5,149.84|
||PgSQL (tunned) |1,407.10 |75.28 |16,837.38 |14,461.00|
||Vendor\Benchmark (Q/sec, Avg) ||SelectAll ||SelectAllJoin||
||ignite thin inmemory |0.42 |0.20|
||ignite jdbc v2 inmemory |0.42 |0.20|
||ignite thin persistence |0.38 |0.16|
||ignite jdbc v2 persistence |0.39 |0.16|
||Mysql (tunned) |0.54 |0.31|
||PgSQL (tunned) |1.92 |0.94|
> 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)
