[ https://issues.apache.org/jira/browse/IGNITE-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704701#comment-16704701 ]
Pavel Kuznetsov commented on IGNITE-10329: ------------------------------------------ Have ran benchmarks on 2 real machines. Note that join query is now: {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.org_id = o.id WHERE salary BETWEEN ? AND ? {noformat} org_id is indexed. Since only one node is tested, affinity key is not required. Ignite and MySQL results (PG tbd): ||Vendor\Benchmark (Q/sec, Avg) ||SimpleSelectBenchmark ||SelectWithJoinBenchmark ||SelectByPkBenchmark|| ||ignite thin inmemory ||879.37 |179.93 |1,051.65| ||ignite thin persistence ||579.15 |142.07 |659.77| ||ignite jdbc v2 inmemory ||903.67 |159.83 |1,059.40| ||ignite jdbc v2 persistence ||631.47 |130.73 |707.26| ||Mysql (tunned) ||776.26 |203.72 |765.58| > 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)