From: "Георгий Кириченко" <georgy@tarantool.org>
To: Konstantin Osipov <kostja@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 2/2] Track wal vclock changes instead of copying
Date: Tue, 12 Feb 2019 22:47:14 +0300 [thread overview]
Message-ID: <1867945.CLyBLBJW6x@home.lan> (raw)
In-Reply-To: <20190212191510.GA10042@chai>
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
On Tuesday, February 12, 2019 10:15:10 PM MSK Konstantin Osipov wrote:
> * Georgy Kirichenko <georgy@tarantool.org> [19/02/12 17:09]:
> > Spare some vclock_copy invocations because they could be expensive.
>
> OK, you did a full-scale diff & merge. This could actually be
> slower than the fast vclock_copy() which is available from the
> previous patch. Let's discuss.
I think in a typical case we wouldn't have more than 1-2-3 active masters so
it could be even faster especially when we have more than 3-4 cluster members.
Also it could be worth if I make some bench for that.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-02-12 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 14:09 [tarantool-patches] [PATCH 0/2] Reduce wal vclock handling complecity Georgy Kirichenko
2019-02-12 14:09 ` [tarantool-patches] [PATCH 1/2] Lightweight vclock_create and vclock_copy Georgy Kirichenko
2019-02-12 19:25 ` [tarantool-patches] " Konstantin Osipov
2019-02-12 19:37 ` Георгий Кириченко
2019-02-12 14:09 ` [tarantool-patches] [PATCH 2/2] Track wal vclock changes instead of copying Georgy Kirichenko
2019-02-12 19:15 ` [tarantool-patches] " Konstantin Osipov
2019-02-12 19:47 ` Георгий Кириченко [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1867945.CLyBLBJW6x@home.lan \
--to=georgy@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 2/2] Track wal vclock changes instead of copying' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox