From dev-return-37520-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Aug 8 00:13:19 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id F03B4180657 for ; Wed, 8 Aug 2018 00:13:18 +0200 (CEST) Received: (qmail 63855 invoked by uid 500); 7 Aug 2018 22:13:18 -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 63843 invoked by uid 99); 7 Aug 2018 22:13:17 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Aug 2018 22:13:17 +0000 Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com [209.85.218.44]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id E25C01F78 for ; Tue, 7 Aug 2018 22:13:16 +0000 (UTC) Received: by mail-oi0-f44.google.com with SMTP id j205-v6so403420oib.4 for ; Tue, 07 Aug 2018 15:13:16 -0700 (PDT) X-Gm-Message-State: AOUpUlHv2CYhUqItRWzy6FZD5ctwsFboekvq+afatm40YyiyBYVHPlMi lmM79ngsdCBilPmpJ6b2fiC7Vyum8qGEPP6FHAiNcA== X-Google-Smtp-Source: AA+uWPwy6y8NpYIbjACbldzPZdC1DDHJnRgL8EipxX2tsfo/6vjmnF+HeoaTHYYaRcY2FjF8u6C0n2NVGc0LbywctmE= X-Received: by 2002:aca:6cc6:: with SMTP id h189-v6mr309345oic.140.1533679996244; Tue, 07 Aug 2018 15:13:16 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:3362:0:0:0:0:0 with HTTP; Tue, 7 Aug 2018 15:12:35 -0700 (PDT) In-Reply-To: References: From: Dmitriy Setrakyan Date: Tue, 7 Aug 2018 17:12:35 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Metrics for MVCC caches To: dev Content-Type: multipart/alternative; boundary="0000000000006035650572dfb307" --0000000000006035650572dfb307 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ivan, To your 2nd question, can you suggest a few MVCC metrics to get the discussion started? D. On Tue, Aug 7, 2018 at 9:17 AM, =D0=9F=D0=B0=D0=B2=D0=BB=D1=83=D1=85=D0=B8= =D0=BD =D0=98=D0=B2=D0=B0=D0=BD wrote: > Hi Igniters, > > I am working on cache metrics support for caches with enabled MVCC. As yo= u > may know, during MVCC transaction execution entry versions are written to > storage right away (without deferring until commit). So, it is not obviou= s > for me if we should update writes count right away or defer it until > commit. On one hand, MVCC entry version write is not "true" write until > commit. On the other hand, it definitely changes the storage. How do we > interpret write metrics in Ignite philosophy? > > Also, it seems that bunch of MVCC specific metrics could be introduced. I > would like to collect some thoughts about it. Which such metrics come to > your mind? > > -- > Best regards, > Ivan Pavlukhin > --0000000000006035650572dfb307--