[
https://issues.apache.org/jira/browse/IGNITE-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730530#comment-17730530
]
Roman Puchkovskiy edited comment on IGNITE-19665 at 6/13/23 2:12 PM:
---------------------------------------------------------------------
There are two problems:
# We go to the configuration to check for table existence each time we obtain
the table
# The check was made less efficient due to changes introduced in IGNITE-19531
Introduction of Catalog and Schema sync will allow us to remove the checks in
item 1 completely, which will automaticlly solve the problem in item 2.
It is suggested to leave this on hold for now until Catalog and Schema sync
arrive or it suddenly turns out that we need all the performance we might get
'right here, right now'.
was (Author: rpuch):
There are two problems:
# We go to the configuration to check for table existence each time we obtain
the table
# The check was made less efficient due to changes introduces in IGNITE-19531
Introduction of Catalog and Schema sync will allow us to remove the checks in
item 1 completely, which will automaticlly solve the problem in item 2.
It is suggested to leave this on hold for now until Catalog and Schema sync
arrive or it suddenly turns out that we need all the performance we might get
'right here, right now'.
> High performance drop in key-value put() operations introduced between May 23
> and June 5
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-19665
> URL: https://issues.apache.org/jira/browse/IGNITE-19665
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Artiukhov
> Priority: Major
> Labels: ignite-3, performance
> Attachments: ai3_embedded_20230606_144606.jfr.zip,
> ai3_thin_client_20230606_075104.jfr.zip, gc.log.20230606_075104,
> ignite-config.conf, ignite3db-0.log, run11-new-emb-jfr.txt, ycsb-run10.log
>
>
> This ticket is a product of subsequent work on
> https://issues.apache.org/jira/browse/IGNITE-19664.
> There are high (more than 4x on my local machine) performance drop in
> {{KeyValueView#put}} operations introduced somewhere between the following
> commit:
> {noformat}
> commit 0c68cbe3f016e508bd9d53ce5320c88acba1acff (HEAD)
> Author: Slava Koptilin <slava.kopti...@gmail.com>
> Date: Tue May 23 10:17:53 2023 +0300
> IGNITE-17883 Removed not implemented 'invoke' functionality (#2090)
> {noformat}
> and the following one:
> {code:java}
> commit a2254434c403bc54685f05e0d6f51bef56abea2a (HEAD -> main, origin/main,
> origin/HEAD)
> Author: Vadim Pakhnushev <8614891+valep...@users.noreply.github.com>
> Date: Mon Jun 5 17:43:07 2023 +0300
> IGNITE-19559 NPE in deploy/undeploy calls in non-REPL mode (#2131)
> {code}
> The test is the "Test 1" from
> https://issues.apache.org/jira/browse/IGNITE-19664, i.e.:
> 1. Start an Ignite 3 server node with attached {{ignite-config.conf}}.
> {{raft.fsync=false}} is set in the config.
> 2. Start YCSB client which makes {{KeyValueView#put}} operations within a
> "100% insert" profile.
> Results for {{0c68cbe3f016e508bd9d53ce5320c88acba1acff}} were as follows:
> {noformat}
> [OVERALL], RunTime(ms), 282482
> [OVERALL], Throughput(ops/sec), 3540.048569466373
> [INSERT], Operations, 1000000
> [INSERT], AverageLatency(us), 1067.488346
> [INSERT], MinLatency(us), 492
> [INSERT], MaxLatency(us), 421375
> [INSERT], 95thPercentileLatency(us), 2059
> [INSERT], 99thPercentileLatency(us), 5151
> [INSERT], Return=OK, 1000000
> {noformat}
> Results for {{a2254434c403bc54685f05e0d6f51bef56abea2a}} are more than 4x
> worse in terms of throughput:
> {code:java}
> [OVERALL], RunTime(ms), 1325870
> [OVERALL], Throughput(ops/sec), 754.2217562807816
> [INSERT], Operations, 1000000
> [INSERT], AverageLatency(us), 5229.54584
> [INSERT], MinLatency(us), 1297
> [INSERT], MaxLatency(us), 164223
> [INSERT], 95thPercentileLatency(us), 9871
> [INSERT], 99thPercentileLatency(us), 14271
> [INSERT], Return=OK, 1000000
> {code}
> Logs for {{0c68cbe3f016e508bd9d53ce5320c88acba1acff}}: see
> https://issues.apache.org/jira/browse/IGNITE-19664
> Logs for {{a2254434c403bc54685f05e0d6f51bef56abea2a}}:
> - node's config: [^ignite-config.conf]
> - node's log: [^ignite3db-0.log]
> - node's GC log: [^gc.log.20230606_075104]
> - YCSB client log: [^ycsb-run10.log]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
