All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hubert Kario <hka@qbs.com.pl>
To: Magicloud Magiclouds <magicloud.magiclouds@gmail.com>
Cc: "linux-btrfs" <linux-btrfs@vger.kernel.org>
Subject: Re: How to fasten btrfs?
Date: Tue, 25 Jan 2011 15:56:51 +0100	[thread overview]
Message-ID: <201101251556.51806.hka@qbs.com.pl> (raw)
In-Reply-To: <AANLkTik_mfFO+ciZbxuuqqRJDkOGoOW=pfjVv0au80TS@mail.gmail.com>

On Tuesday, January 25, 2011 15:28:11 Magicloud Magiclouds wrote:
> So you were saying that, even an unlink operation, the system walks
> through all file data blocks? I thought unlink wouldn't have to write
> too much data.

No, but the amount of data to be changed if the number of extents is sm=
all=20
will be lower.

>=20
> On Tue, Jan 25, 2011 at 6:30 PM, Hubert Kario <hka@qbs.com.pl> wrote:
> > On Tuesday 25 of January 2011 07:45:02 Magicloud Magiclouds wrote:
> >> Hi,
> >>   I am using 2.6.36.3 kernel with btrfs, 512MB memory and a very s=
low
> >> disk, no special options for mounting btrfs except noatime. Now I
> >> found it very slow. When I rm a 5GB movie, it took 20 secs.
> >=20
> > try mounting with nodatacow and defragment the directory the file r=
esides
> > in
> >=20
> > Regards
> > --
> > Hubert Kario
> > QBS - Quality Business Software
> > 02-656 Warszawa, ul. Ksawer=C3=B3w 30/85
> > tel. +48 (22) 646-61-51, 646-74-24
> > www.qbs.com.pl

--=20
Hubert Kario
QBS - Quality Business Software
02-656 Warszawa, ul. Ksawer=C3=B3w 30/85
tel. +48 (22) 646-61-51, 646-74-24
www.qbs.com.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2011-01-25 14:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25  6:45 How to fasten btrfs? Magicloud Magiclouds
2011-01-25 10:30 ` Hubert Kario
2011-01-25 14:28   ` Magicloud Magiclouds
2011-01-25 14:56     ` Hubert Kario [this message]

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=201101251556.51806.hka@qbs.com.pl \
    --to=hka@qbs.com.pl \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=magicloud.magiclouds@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.