From: Tobias <tracer@robotech.de>
To: Liu Bo <liubo2009@cn.fujitsu.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Extreme slowdown
Date: Fri, 16 Dec 2011 09:51:56 +0100 [thread overview]
Message-ID: <4EEB06AC.4070500@robotech.de> (raw)
In-Reply-To: <4EEAA86C.4080706@cn.fujitsu.com>
Am 16.12.2011 03:09, schrieb Liu Bo:
> On 12/16/2011 02:49 AM, Tobias wrote:
>> Any hints how i could speed it up?
>>
>
> I recommend to run defragment on your files,
> it should help you, although defrag maybe slow, too.
>
When deleting files does it matter if the data is fragmented?
When i do normal file-access the speed of reading is ok so until not i
didn't care about fragmentation. Especially because the data isn't
changes after the first write.
Can i do a defrag on the metadata only?
Tobias
next prev parent reply other threads:[~2011-12-16 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 18:49 Extreme slowdown Tobias
2011-12-16 2:09 ` Liu Bo
2011-12-16 8:51 ` Tobias [this message]
2011-12-16 9:11 ` Hugo Mills
2011-12-16 2:19 ` Fajar A. Nugraha
2011-12-16 3:44 ` Chester
2011-12-16 4:15 ` Shyam Prasad N
2011-12-16 9:09 ` Tobias
2011-12-16 9:19 ` Sander
2011-12-16 17:45 ` Tobias
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=4EEB06AC.4070500@robotech.de \
--to=tracer@robotech.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).