You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2022/09/27 08:08:00 UTC
[jira] [Updated] (IGNITE-17764) Performance drop on index.find operation after IGNITE-17046
[ https://issues.apache.org/jira/browse/IGNITE-17764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov updated IGNITE-17764:
---------------------------------------
Attachment: IndexFindBenchmark.java
> 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: Major
> Attachments: IndexFindBenchmark.java
>
>
> There is performance drop on index.find operation after IGNITE-17046 was merged.
> Can be reproduced with the JMH benchmark.
> 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)