Tarantool development patches archive
 help / color / mirror / Atom feed
From: Konstantin Osipov <kostja@tarantool.org>
To: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 2/2] vinyl: don't compress L1 runs
Date: Thu, 11 Apr 2019 10:28:44 +0300	[thread overview]
Message-ID: <20190411072844.GA31100@chai> (raw)
In-Reply-To: <2887580c0693a777c80a64a5bffb329578f79b3f.1554905969.git.vdavydov.dev@gmail.com>

* Vladimir Davydov <vdavydov.dev@gmail.com> [19/04/10 18:12]:
> L1 runs are usually the most frequently read and smallest runs at the
> same time so we gain nothing by compressing them.

OK to push.
> 
> Closes #2389

I might want to open another ticket which would ensure all levels
except the last two are left uncompressed.


-- 
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov

  reply	other threads:[~2019-04-11  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 14:22 [PATCH 1/2] xlog: cleanup setting of write options Vladimir Davydov
2019-04-10 14:22 ` [PATCH 2/2] vinyl: don't compress L1 runs Vladimir Davydov
2019-04-11  7:28   ` Konstantin Osipov [this message]
2019-04-11 10:24     ` [tarantool-patches] " Vladimir Davydov

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=20190411072844.GA31100@chai \
    --to=kostja@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH 2/2] vinyl: don'\''t compress L1 runs' \
    /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