From: Shridhar Daithankar <ghodechhap@ghodechhap.net>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: unclean shutdown and space cache rebuild
Date: Mon, 01 Jul 2013 21:49:16 +0530 [thread overview]
Message-ID: <1792894.GCCHX1XfTr@bheem> (raw)
In-Reply-To: <pan$d6b02$c375f8e3$e64c63ed$cc12d244@cox.net>
On Monday, July 01, 2013 09:10:41 AM Duncan wrote:
> > But in general, how to find out most fragmented files and folders?
> > mouting with autodefrag is a serious degradation..
>
> It is? AFAIK, all the autodefrag mount option does is scan files for
> fragmentation as they are written and queue any fragmentation-detected
> files for background defrag by the defrag thread.
>
> I had expected, particularly on spinning rust, that the benefits of
> autodefrag to far exceed the costs, so your performance drag claim is
> interesting to me indeed. If my expectation is wrong, which it could be,
> I'd love to know why, and see some numbers.
while I don't have numbers, I enabled autodefrag on all the partitions and
rebooted(twice, just to confirm) and its slow..
everything has a 10 second tail of disk activity and has quite some visible
latency. Moving mouse, switching windows, starting new programs, everything
has visible latency thats unusable.
It seems autodefrag is being too aggressive for its own good..
I am sticking with defragging folders individually. /var, /home and a 1GB
squid cache is what I have narrowed down and things are reasonably fast.
--
Regards
Shridhar
next prev parent reply other threads:[~2013-07-01 16:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 13:56 unclean shutdown and space cache rebuild Shridhar Daithankar
2013-06-30 17:53 ` Garry T. Williams
2013-06-30 19:58 ` Pete
2013-06-30 20:10 ` Clemens Eisserer
2013-06-30 21:20 ` Duncan
2013-06-30 23:12 ` Roger Binns
2013-07-01 2:50 ` Shridhar Daithankar
2013-07-01 9:10 ` Duncan
2013-07-01 16:19 ` Shridhar Daithankar [this message]
2013-07-02 13:00 ` Duncan
2013-07-02 15:49 ` Shridhar Daithankar
2013-07-05 3:45 ` Shridhar Daithankar
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=1792894.GCCHX1XfTr@bheem \
--to=ghodechhap@ghodechhap.net \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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).