From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f67.google.com (mail-lf1-f67.google.com [209.85.167.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 071B1452566 for ; Thu, 14 Nov 2019 16:44:24 +0300 (MSK) Received: by mail-lf1-f67.google.com with SMTP id v8so5061063lfa.12 for ; Thu, 14 Nov 2019 05:44:24 -0800 (PST) Date: Thu, 14 Nov 2019 16:44:22 +0300 From: Konstantin Osipov Message-ID: <20191114134422.GA8372@atlas> References: <20191114125705.26760-1-maria.khaydich@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191114125705.26760-1-maria.khaydich@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH] Trigger on vclock change List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Maria Cc: tarantool-patches@dev.tarantool.org * Maria [19/11/14 15:59]: > This patch implements replication.on_vclock > trigger that can be useful for programming > shard-systems with redundancy. 3808 is about being able to wait for an lsn. Using a trigger for *waiting* is called busy waiting, and is a cpu hog, especially at a performance critical space like update of replica vclock, which can happen a hundred times a second. Why not implement a way to wait for an lsn instead? -- Konstantin Osipov, Moscow, Russia