[cc the XFS list again]
On Tue, Feb 24, 2015 at 05:57:00PM -0500, Dave Hall wrote:
> I'm not going to post any more of my noob questions.
Which defeats the purpose of having a public, archived list - other
people can find your questions and the answers through search
engines like Google.
> Sounds like
> about the best I could do would be to get a faster HBA (planned) and
> just go for it. Also sounds like I might want to look at breaking
> up some the large rsyncs that are running inside rsnapshot. Perhaps
> it's just the directory tree traversal that's killing my
Most likely - that's small, random IO and will almost always be seek
bound on spinning disks.
> One last question - format options: I seem to recall that there are
> some parameters on the mkfs - su, sw, etc. Do I need to specify
> those when I set up this new volume or can mkfs.xfs calculate them
> correctly, now?
XFS has calculated them correctly for years when you are using MD or
LVM for software striping. Nowdays it even works with some hardware
RAID, but support is still vendor and hardware specific. That's when
you may have to specify it manually, as per the FAQ:
> Also, I saw something about formatting differently
> for a workload like email with many small files, vs. a media
> workload that's focused on large files. Since rsnapshot has to
> create a new directory tree for every snapshot I'm going to say it's
> closer to the email workload. Any guidance on that?
Set up your storage config to be optimal for your workload, and XFS
should set it's defaults appropriately. If you have a random seek
bound workload, though, there's very little you can tweak at the
filesystem level that will make any significant different to
performance. In these cases, It's better to buy big, cheap SSDs than
expensive spinning disks if you need better performance for this
sort of workload.