From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yk0-f177.google.com ([209.85.160.177]:62011 "EHLO mail-yk0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752328AbbBMNId (ORCPT ); Fri, 13 Feb 2015 08:08:33 -0500 Received: by mail-yk0-f177.google.com with SMTP id 20so7550726yks.8 for ; Fri, 13 Feb 2015 05:08:33 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <54DC9AB9.7030505@gmail.com> References: <62ntqb-o2r.ln1@hurikhan77.spdns.de> <54DC9AB9.7030505@gmail.com> Date: Fri, 13 Feb 2015 14:08:33 +0100 Message-ID: Subject: Re: btrfs performance, sudden drop to 0 IOPs From: "P. Remek" To: Austin S Hemmelgarn Cc: Kai Krakow , linux-btrfs@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: > I'd definitely suggest using NOCOW for any file you are doing O_DIRECT with, > as you should see _much_ better performance that way, and also don't run the > (theoretical) risk of some of the same types of corruption that swapfiles on > BTRFS can cause. I mounted the filesystem with nodatacow as follows and it didn't help - it still drops to 0 IOPs every couple of seconds. /dev/sdi on /mnt/btrfs type btrfs (rw,nodatacow)