[jira] [Updated] (IGNITE-20869) CompletableFuture with orTimeout has noticeable performance impact
[ https://issues.apache.org/jira/browse/IGNITE-20869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-20869: - Labels: ignite-3 (was: ) > CompletableFuture with orTimeout has noticeable performance impact > -- > > Key: IGNITE-20869 > URL: https://issues.apache.org/jira/browse/IGNITE-20869 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > [This > |https://github.com/apache/ignite-3/blob/82c74598b5006ea3e4e86da744a68022dd799c89/modules/network/src/main/java/org/apache/ignite/network/DefaultMessagingService.java#L254-L255]line > of code cost us near the 3us from the 26us of the whole query (~10%). The > reason is the orTimeout(...) call. > The simple switch to simple new CompletableFuture() give us 10% boost from > 26us/s to 23us/s in the 1-node fsync=false run of SelectBenchmark.kvGet. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20869) CompletableFuture with orTimeout has noticeable performance impact
[ https://issues.apache.org/jira/browse/IGNITE-20869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov updated IGNITE-20869: Description: [This |https://github.com/apache/ignite-3/blob/82c74598b5006ea3e4e86da744a68022dd799c89/modules/network/src/main/java/org/apache/ignite/network/DefaultMessagingService.java#L254-L255]line of code cost us near the 3us from the 26us of the whole query (~10%). The reason is the orTimeout(...) call. The simple switch to simple new CompletableFuture() give us 10% boost from 26us/s to 23us/s in the 1-node fsync=false run of SelectBenchmark.kvGet. was: [This |https://github.com/apache/ignite-3/blob/82c74598b5006ea3e4e86da744a68022dd799c89/modules/network/src/main/java/org/apache/ignite/network/DefaultMessagingService.java#L254-L255]line of code cost us near the 3us from the 26us of the whole query (~10%). The reason is the orTimeout(...) call. > CompletableFuture with orTimeout has noticeable performance impact > -- > > Key: IGNITE-20869 > URL: https://issues.apache.org/jira/browse/IGNITE-20869 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Gusakov >Priority: Major > > [This > |https://github.com/apache/ignite-3/blob/82c74598b5006ea3e4e86da744a68022dd799c89/modules/network/src/main/java/org/apache/ignite/network/DefaultMessagingService.java#L254-L255]line > of code cost us near the 3us from the 26us of the whole query (~10%). The > reason is the orTimeout(...) call. > The simple switch to simple new CompletableFuture() give us 10% boost from > 26us/s to 23us/s in the 1-node fsync=false run of SelectBenchmark.kvGet. -- This message was sent by Atlassian Jira (v8.20.10#820010)
