From dev-return-48826-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Dec 23 10:44:22 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 6F8BD18061A for ; Mon, 23 Dec 2019 11:44:22 +0100 (CET) Received: (qmail 39633 invoked by uid 500); 23 Dec 2019 10:44:21 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 39621 invoked by uid 99); 23 Dec 2019 10:44:21 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Dec 2019 10:44:21 +0000 Received: from mail-io1-f51.google.com (mail-io1-f51.google.com [209.85.166.51]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 64E324FB3 for ; Mon, 23 Dec 2019 10:44:21 +0000 (UTC) Received: by mail-io1-f51.google.com with SMTP id z193so15739772iof.1 for ; Mon, 23 Dec 2019 02:44:21 -0800 (PST) X-Gm-Message-State: APjAAAVVOh/KZ/8UjubvHC6oe3O07E+oJIOPYeFVGC7OmYnmCR4P0zv3 RYsgbpiyF0Q4StCTUOw6mO2ShboshDRCklYgONA= X-Google-Smtp-Source: APXvYqzZ8siQ4Bh6ZZnjRtpmHq3NXKc9p5F8Lo/IlxojqVNEwzxnggfBPdU0A91Dr/dMscPgjE/5C7z9iauIbBZml/Y= X-Received: by 2002:a6b:1587:: with SMTP id 129mr18903301iov.117.1577097860991; Mon, 23 Dec 2019 02:44:20 -0800 (PST) MIME-Version: 1.0 From: Anton Vinogradov Date: Mon, 23 Dec 2019 13:44:10 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: PME speedup #2, TX recovery delay elimination. To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="000000000000c7cf24059a5cb517" --000000000000c7cf24059a5cb517 Content-Type: text/plain; charset="UTF-8" Igniters, One more PME optimization ready to be reviewed. I found a strange tx recovery delay caused by IGNITE_TX_SALVAGE_TIMEOUT. I've checked the code and tests and found no reason to delay recovery. So, the issue [1] is ready to be reviewed. Improvement checked with benchmark [2] and fix, obviously, 100 ms faster :) [1] https://issues.apache.org/jira/browse/IGNITE-12272 [2] https://github.com/anton-vinogradov/ignite/commit/f8c27253b0ecfe7381418f505aafe942efe5a0a8 --000000000000c7cf24059a5cb517--