[
https://issues.apache.org/jira/browse/IGNITE-17764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609973#comment-17609973
]
Taras Ledkov commented on IGNITE-17764:
---------------------------------------
Benchmark results *IgniteSqlQueryBenchmark*
|| branch || ops/sec || ||
| ignite-2.13 | 81,804.13 | - |
| ignite-2.14 | 75,938.40 | {color:#DE350B}*-7.2%*{color} |
| IGNITE-17764 | 80,412.17 | {color:#00875A}*-1.2% *{color} |
[~alex_pl], the performance drop appears to have been fixed.
> Performance drop on index.find operation after IGNITE-17046
> -----------------------------------------------------------
>
> Key: IGNITE-17764
> URL: https://issues.apache.org/jira/browse/IGNITE-17764
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.14
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Blocker
> Fix For: 2.14
>
> Attachments: IndexFindBenchmark.java, benchmark-report.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There is performance drop on index.find operation after IGNITE-17046 was
> merged.
> Can be reproduced with the following JMH benchmark: [^IndexFindBenchmark.java]
> Results before 17046:
> {noformat}
> IndexFindBenchmark.findOneIndex thrpt 5 393,468 ± 10,775 ops/ms
> IndexFindBenchmark.findThreeIndexes thrpt 5 95,408 ± 4,671 ops/ms
> {noformat}
> Results after 17046:
> {noformat}
> IndexFindBenchmark.findOneIndex thrpt 5 333,311 ± 11,894 ops/ms
> IndexFindBenchmark.findThreeIndexes thrpt 5 85,693 ± 1,441 ops/ms
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
