[PATCH] vinyl: take into account primary key lookup in latency accounting

[Vladimir Davydov]

On Thu, Apr 11, 2019 at 11:04:34PM +0300, Konstantin Osipov wrote:
> * Vladimir Davydov <vdavydov.dev at gmail.com> [19/04/11 20:29]:
> > Currently, latency accounting and warning lives in vy_point_lookup and
> > vy_read_iterator_next. As a result, we don't take into account full by
> > partial tuple lookup in it while it can take quite a while, especially
> > if there are lots of deferred DELETE statements we have to skip. So this
> > patch moves latency accounting to the upper level, namely to vy_get and
> > vinyl_iterator_{primary,secondary}_next.
> 
> I believe this si a temporary patch as long as it uses
> clock_monotonic :)

It doesn't. I just moves latency accounting to the upper level to take
into account the time spent on skipping deferred DELETEs. It still uses
ev_monotonic_now for latency accounting.