You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/12/03 10:05:00 UTC

[jira] [Commented] (IGNITE-10329) Create JDBC "query" and "query join" benchmarks and compare them with Postgres and MySQL

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

Vladimir Ozerov commented on IGNITE-10329:
------------------------------------------

[~pkouznet], my comments:
1) Lets change LEFT JOIN to INNER JOIN, as it adds unnecessary complexity
2) Let's add a benchmark with JOIN which will return person by ID
3) Let's add scan benchmark which return all persons
4) The same as p.3, but with JOIN with organization

> 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)