From: Dave Chinner <david@fromorbit.com>
To: Pedro Ribeiro <pedrib@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Improving XFS desktop performance?
Date: Fri, 20 Nov 2009 17:43:16 +1100 [thread overview]
Message-ID: <20091120064316.GB3804@discord.disaster> (raw)
In-Reply-To: <74fd948d0911191805m30c34b51m97c2a998dbe0bac3@mail.gmail.com>
On Fri, Nov 20, 2009 at 02:05:01AM +0000, Pedro Ribeiro wrote:
> And on /etc/fstab mount it as;
> /dev/mapper/target noatime,logbufs=8,logbsize=256k
>
> After the above, my delete speed improved drastically.
That would be the logbsize option your specified - logbufs=9 is the
default.
> Searching around the net I was able to find that using "lazy-count=1"
> on mkfs would give a performance increase - how much would that be,
> enough for me to do a full backup, format with that option + 128m log
> and then restore all again?
It depends on your workload. If you are doing lots of stuff in
parallel, then it makes a big difference because it removes the
superblock as a single point of contention. It also has the effect
of reducing the latency of fsync() if allocation was required.
Neither will affect typical desktop workloads unless you are
doing multi-media work, in which case the latency reduction of
lazy-count=1 make a big difference.
> And anything else you recommend?
No, the defaults set most of the best options for performance.
We probably should set lazy-count=1 as the default now that most
distros have picked up kernels that support that option now.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-11-20 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 2:05 Improving XFS desktop performance? Pedro Ribeiro
2009-11-20 5:29 ` Eric Sandeen
2009-11-20 6:43 ` Dave Chinner [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=20091120064316.GB3804@discord.disaster \
--to=david@fromorbit.com \
--cc=pedrib@gmail.com \
--cc=xfs@oss.sgi.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