[ 
https://issues.apache.org/jira/browse/IGNITE-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729778#comment-17729778
 ] 

Ivan Artukhov commented on IGNITE-19665:
----------------------------------------

Results of the "Test 2. Embedded mode" from for the "new" commit 
{{a2254434c403bc54685f05e0d6f51bef56abea2a}} are the same as for "old" 
{{0c68cbe3f016e508bd9d53ce5320c88acba1acff}} from 
https://issues.apache.org/jira/browse/IGNITE-19664:

{code:java}
[OVERALL], RunTime(ms), 175194
[OVERALL], Throughput(ops/sec), 5707.958035092526
[INSERT], Operations, 1000000
[INSERT], AverageLatency(us), 638.186869
[INSERT], MinLatency(us), 253
[INSERT], MaxLatency(us), 479487
[INSERT], 95thPercentileLatency(us), 1342
[INSERT], 99thPercentileLatency(us), 3825
[INSERT], Return=OK, 1000000
{code}

YCSB log:  [^run11-new-emb-jfr.txt] 
JFR:  [^ai3_embedded_20230606_144606.jfr.zip] 

> 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 Artukhov
>            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)

Reply via email to