You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2023/12/08 12:59:00 UTC
[jira] [Updated] (IGNITE-20808) Sql. Poor performance of INSERT

     [ https://issues.apache.org/jira/browse/IGNITE-20808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Orlov updated IGNITE-20808:
--------------------------------------
    Description: 
It's expected that sql INSERT is currently slower than kv puts because sql lacks partition pruning. But even on a single-partition table (this case should not be affected by lack of partition pruning) INSERT is 5x times slower than kv.

Let's investigate performance of sql INSERT. 

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.kvInsert | 1 | false | 1 | avgt | 20 | 0.153 | ± 0.019 | ms/op |
| InsertBenchmark.sqlInsert | 1 | false | 1 | avgt | 20 | 0.657 | ± 0.056 | ms/op |

  was:
It's expected that sql INSERT is currently slower than kv puts because sql lacks partition pruning. But even on a single-partition table (this case should not be affected by lack of partition pruning) INSERT is 5x times slower than kv.

Let's investigate and fix performance of sql INSERT. 

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.kvInsert | 1 | false | 1 | avgt | 20 | 0.153 | ± 0.019 | ms/op |
| InsertBenchmark.sqlInsert | 1 | false | 1 | avgt | 20 | 0.657 | ± 0.056 | ms/op |


> Sql. Poor performance of INSERT
> -------------------------------
>
>                 Key: IGNITE-20808
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20808
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Assignee: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>
> It's expected that sql INSERT is currently slower than kv puts because sql lacks partition pruning. But even on a single-partition table (this case should not be affected by lack of partition pruning) INSERT is 5x times slower than kv.
> Let's investigate performance of sql INSERT. 
> 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.kvInsert | 1 | false | 1 | avgt | 20 | 0.153 | ± 0.019 | ms/op |
> | InsertBenchmark.sqlInsert | 1 | false | 1 | avgt | 20 | 0.657 | ± 0.056 | ms/op |



--
This message was sent by Atlassian Jira
(v8.20.10#820010)