From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com
Cc: stan@hardwarefreak.com,
Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Subject: Re: suddenly slow writes on XFS Filesystem
Date: Mon, 7 May 2012 10:21:14 +0200 [thread overview]
Message-ID: <201205071021.14478.Martin@lichtvoll.de> (raw)
In-Reply-To: <4FA76E11.1070708@profihost.ag>
Am Montag, 7. Mai 2012 schrieb Stefan Priebe - Profihost AG:
> Hi,
>
> after deleting 400GB it was faster. Now there are still 300GB free but
> it is slow as hell again ;-(
Well, before you had 200 GB free, now you have 300 GB free. Thats not that
much more. You have 5 AGs, so if distributed evenly it would be 40 to 60
GB free space per AG.
The 10% Dave recommended of 4,6 TB would be 460 GB.
Are other volumes of similar size are similarily full but faster?
Would be interesting to see whether you are able to sustain faster speeds
by keeping the volume above 500 GB free or so.
> >> It is a raid 10 of 20 SATA Disks and i can only write to them with
> >> about 700kb/s while doing random i/o.
> >
> > What sort of random IO? size, read, write, direct or buffered, data
> > or metadata, etc?
>
> There are 4 rsync processes running and doing backups of other severs.
Which rsync version is involved? I strongly suggest to use rsync version 3
or above.
> > Your filesystem is near full - the allocation algorithms definitely
> > slow down as you approach ENOSPC, and IO efficiency goes to hell
> > because of a lack of contiguous free space to allocate from.
>
> I've now 94% used but it is still slow. It seems it was just getting
> fast with more than 450GB free space.
>
> /dev/sdb1 4,6T 4,3T 310G 94% /mnt
Then: Will it stay fast if you keep it above 450 GB free space?
And is it as fast then as it used to be before you faced performance
issues?
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-07 8:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 9:01 suddenly slow writes on XFS Filesystem Stefan Priebe
2012-05-06 10:31 ` Martin Steigerwald
2012-05-06 10:33 ` Martin Steigerwald
2012-05-06 15:45 ` Stan Hoeppner
2012-05-06 19:25 ` Stefan Priebe
2012-05-07 1:39 ` Dave Chinner
2012-05-06 21:43 ` Martin Steigerwald
2012-05-07 6:40 ` Stefan Priebe - Profihost AG
2012-05-07 1:34 ` Dave Chinner
2012-05-07 6:39 ` Stefan Priebe - Profihost AG
2012-05-07 7:17 ` Dave Chinner
2012-05-07 7:22 ` Stefan Priebe - Profihost AG
2012-05-07 16:36 ` Stan Hoeppner
2012-05-07 19:08 ` Martin Steigerwald
2012-05-07 20:05 ` Stefan Priebe
2012-05-09 6:57 ` Stan Hoeppner
2012-05-09 7:04 ` Dave Chinner
2012-05-09 7:36 ` Stefan Priebe - Profihost AG
2012-05-09 7:49 ` Stan Hoeppner
2013-02-15 15:06 ` 32bit apps and inode64 Stefan Priebe - Profihost AG
2013-02-15 21:46 ` Ben Myers
2013-02-16 10:24 ` Stefan Priebe - Profihost AG
2013-02-17 21:33 ` Dave Chinner
2013-02-18 8:12 ` Stefan Priebe - Profihost AG
2013-02-18 22:06 ` Dave Chinner
2013-02-17 8:13 ` Jeff Liu
2013-02-19 19:11 ` Ben Myers
2012-05-07 23:42 ` suddenly slow writes on XFS Filesystem Dave Chinner
2012-05-07 8:21 ` Martin Steigerwald [this message]
2012-05-07 16:44 ` Stan Hoeppner
2012-05-07 8:31 ` Martin Steigerwald
2012-05-07 13:57 ` Stefan Priebe - Profihost AG
2012-05-07 14:32 ` Martin Steigerwald
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=201205071021.14478.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=s.priebe@profihost.ag \
--cc=stan@hardwarefreak.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.