From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Snitzer Subject: Re: Thinly-Provisioned Logical Volumes Date: Mon, 22 Sep 2014 08:38:38 -0400 Message-ID: <20140922123837.GA5191@redhat.com> References: Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: lilofile Cc: Ondrej Kozina , device-mapper development , "Alasdair G. Kergon" List-Id: dm-devel.ids On Sat, Sep 20 2014 at 10:19am -0400, lilofile wrote: > when I test Thinly-Provisioned Logical Volumes(use device thinprovison > target),I found the random write performance is very low. What factors > will influence the random write performance of thin volume. It is worth reading this blog post from Joe: http://device-mapper.org/blog/2014/01/21/random-io-and-copy-on-write-schemes/ > how can i quickly understand dm-bufio.c? What is it you'd like to know? dm-bufio.c isn't the smoking gun for random write performance being slow though. It is more to do with the natural impact random writes have on thinp (as discussed in the above article).