From: Jens Rosenboom <j.rosenboom@syseleven.de>
To: xfs@oss.sgi.com
Subject: Performance problem with multiple parallel rm -rf's
Date: Wed, 02 Dec 2009 11:02:08 +0100 [thread overview]
Message-ID: <4B163B20.6030808@syseleven.de> (raw)
On a large 13TB XFS volume that is being used for backups, I am seeing
bad performance if multiple "rm -rf" processes are running in parallel.
The backups are being done with rsnapshot and the first operation it
does is removing the oldest snapshot. A single rsnapshot does this in
reasonable time, but if four jobs are started at the same time, all
their rm processes run for hours without making much progress.
This seems to be related to the planned optimizations in
http://xfs.org/index.php/Improving_Metadata_Performance_By_Reducing_Journal_Overhead
Are there any other tuning options I might try? I'm already using
"noatime,nodiratime,nobarrier,logbufs=8,logbsize=256k" as mount options
and did enable lazy_counters for the fs.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-12-02 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 10:02 Jens Rosenboom [this message]
2009-12-02 11:41 ` Performance problem with multiple parallel rm -rf's Sujit K M
2009-12-02 14:49 ` Justin Piszcz
2009-12-03 1:05 ` Dave Chinner
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=4B163B20.6030808@syseleven.de \
--to=j.rosenboom@syseleven.de \
--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