linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 05 Jul 2013 09:15:13 +0530	[thread overview]
Message-ID: <4656105.EoWWoPheHC@bheem> (raw)
In-Reply-To: <14300696.s96c8th5lD@bheem>

On Tuesday, July 02, 2013 09:19:07 PM Shridhar Daithankar wrote:
> On Tuesday, July 02, 2013 01:00:29 PM Duncan wrote:
> > But I'd still expect there to be some better performance steady state
> > after a few mounts gets the basic filesystem defragged.  Tho if the
> > fileystem is heavily fragmented[2], in practice it may well be easier to
> > backup the filesystem content, do a clean mkfs and mount with autodefrag
> > and restore from backup, thus ensuring autodefrag is on while filling the
> > filesystem in the first place, than to wait for autodefrag to reach a
> > stable system state in normal operation over many mounts.
> 
> well, I think I will bite the bullet and defrag entire / overnight and
> repeat the autodefrag mount option. That should work too.

and that worked. defragged all the mount points including files and dirs, 
enabled autodefrag and reboot. Took about 2 hour to defrag the existing files.

but the filesystem is now extremely smooth. faster than ext4 I might say. sure 
there are occasional stalls but they are more of noticable than annoyance and 
thats pretty much compensated by the significant improvement in latency in 
everything.

fun fact, pg_test_fsync now reports 44 fsyncs per seconds instead of earlier 
20. I don't know if that down to defragmentation or compression.

Also another bigger disk of 500GB, the score is around 24 fsyncs per second. 
So I suspect it has to do with tree size.

anyways, good things overall

thanks for the help and suggestions.


-- 
Regards
 Shridhar

      reply	other threads:[~2013-07-05  3:39 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
2013-07-02 13:00         ` Duncan
2013-07-02 15:49           ` Shridhar Daithankar
2013-07-05  3:45             ` Shridhar Daithankar [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=4656105.EoWWoPheHC@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).