[
https://issues.apache.org/jira/browse/IGNITE-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698747#comment-16698747
]
Pavel Kuznetsov commented on IGNITE-10329:
------------------------------------------
Updated results.
Dataset : 1M rows Person and 100K rows Organization, ~600 MB in total.
Postgresql v11.1
Mysql (InnoDb) v8.0.13
Ignite both persistence on and off has 10GiB inmemory data region.
"tunned" means tunned parameters {{innodb_buffer_pool_size = 10G}} and
{{shared_buffers = 10GB}}
*Simple select:* {{SELECT ID FROM PUBLIC.PERSON WHERE SALARY BETWEEN ? AND ?}}
|| Vendor || Queries/sec, Avg ||
| Ignite (inmemory) | 5.48 |
| MySQL (tunned) | 17.36 |
| Postgres (tunned) | 37.15 |
| Ignite (persistence) | 3.39 |
*Select with join:*
{noformat}
SELECT p.id, p.org_id, p.first_name, p.last_name, p.salary, o.name
FROM PUBLIC.PERSON p
LEFT JOIN PUBLIC.ORGANIZATION o
ON p.id = o.id
WHERE salary BETWEEN ? AND ?
{noformat}
|| Vendor || Queries/sec, Avg ||
| Ignite (inmemory) | 5.61 |
| MySQL (tunned) | 10.44 |
| Postgres (tunned) | 36.32 |
| Ignite (persistence) | 3.36 |
> 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)
