[
https://issues.apache.org/jira/browse/IGNITE-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-20812:
---------------------------------------
Epic Link: IGNITE-21312
> Sql. Performance of a queries affected by number of partitions
> --------------------------------------------------------------
>
> Key: IGNITE-20812
> URL: https://issues.apache.org/jira/browse/IGNITE-20812
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> Performance of INSERT and SELECT by primary key queries is affected by number
> of partitions in the table. Most probably, the reason is a lack of partition
> pruning in sql engine.
> Let's investigate and fix the problem.
> Here is a result of local (on my laptop; 2,6 GHz 6-Core Intel Core i7 32GB
> RAM) benchmark:
> ||Benchmark||(clusterSize)||(fsync)||(partitionCount)||Mode||Cnt||Score||Error||Units||
> |InsertBenchmark.sqlInsert|1|false|1|avgt|20|0.643|± 0.069|ms/op|
> |InsertBenchmark.sqlInsert|1|false|5|avgt|20|0.756|± 0.049|ms/op|
> |InsertBenchmark.sqlInsert|1|false|25|avgt|20|1.114|± 0.093|ms/op|
> |SelectBenchmark.sqlGet|1|false|1|avgt|20|203.432|± 16.617|us/op|
> |SelectBenchmark.sqlGet|1|false|5|avgt|20|320.383|± 22.086|us/op|
> |SelectBenchmark.sqlGet|1|false|25|avgt|20|794.232|± 49.473|us/op|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
