From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kostja@tarantool.org>
Date: Tue, 23 Oct 2018 11:46:07 +0300
From: Konstantin Osipov <kostja@tarantool.org>
Subject: Re: [tarantool-patches] Re: [PATCH 0/5] Delete old WAL files if
 running out of disk space
Message-ID: <20181023084607.GB16100@chai>
References: <cover.1538942600.git.vdavydov.dev@gmail.com>
 <20181016190522.GH5454@chai>
 <20181017082058.ebdyx3kwk42ln5tw@esperanza>
 <20181023083734.pkgdqhvyp3bvepgh@esperanza>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20181023083734.pkgdqhvyp3bvepgh@esperanza>
To: Vladimir Davydov <vdavydov.dev@gmail.com>
Cc: tarantool-patches@freelists.org
List-ID: <tarantool-patches.dev.tarantool.org>

* Vladimir Davydov <vdavydov.dev@gmail.com> [18/10/23 11:42]:
> Alas, I was wrong. Even though the synthetic test shows a great
> improvement when fallocate() is used, there's practically no difference
> in case of nosqlbench. So the feature doesn't seem to be worthwhile.
> I guess I'll reimplement WAL auto-removal without fallocate().

Well, wait. This is the same thing I observed on my ssd machine.
The good thing is that it doesn't make things worse. 

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