From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <vdavydov.dev@gmail.com>
Date: Tue, 17 Jul 2018 13:14:52 +0300
From: Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: [RFC PATCH 03/23] vinyl: use vy_mem_iterator for point lookup
Message-ID: <20180717101452.7izxzfjac3qq3jcv@esperanza>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4d3521ff4e0b6e30f96ad0cb7443216418dbda29.1531065648.git.vdavydov.dev@gmail.com>
References: <cover.1531065648.git.vdavydov.dev@gmail.com>
 <4d3521ff4e0b6e30f96ad0cb7443216418dbda29.1531065648.git.vdavydov.dev@gmail.com>
To: tarantool-patches@freelists.org
Cc: kostja@tarantool.org
List-ID: <tarantool-patches.dev.tarantool.org>

On Sun, Jul 08, 2018 at 07:48:34PM +0300, Vladimir Davydov wrote:
> vy_mem_iterator_next is as effecient as the current implementation of
> vy_point_lookup_scan_mem, because it doesn't copy statements anymore
> (see commit 1e1c1fdbedd vinyl: make read iterator always return newest
> tuple version). Let's use it instead of open-coding vy_mem tree lookup.
> ---
>  src/box/vy_point_lookup.c | 47 +++++++++--------------------------------------
>  1 file changed, 9 insertions(+), 38 deletions(-)

Kostja pushed this one a while ago.