[Top] [All Lists]

Re: xfs tuning for a 830 GB partition (mkfs.xfs options)

To: xfs@xxxxxxxxxxx
Subject: Re: xfs tuning for a 830 GB partition (mkfs.xfs options)
From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Date: Wed, 08 Dec 2010 18:27:50 -0600
In-reply-to: <AANLkTi=qkM9c5ukdJj7Hqhj8XMWSOGNENLEG9_Uz_DBT@xxxxxxxxxxxxxx>
References: <AANLkTimkZB20eqywSPvwh00gcXWcr4_Eqm5u40P6RqaJ@xxxxxxxxxxxxxx> <4D00032D.4040000@xxxxxxxxxxxxxxxxx> <AANLkTi=qkM9c5ukdJj7Hqhj8XMWSOGNENLEG9_Uz_DBT@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv: Gecko/20101027 Thunderbird/3.1.6
Abel Coto put forth on 12/8/2010 5:29 PM:

> By the moment i will use one hard disk for / (on ext3) and /home , and
> the data partition for saving 3d projects working on in another hard
> disk (1,5 tb one , with the 350 GB partition and one of 1 TB for
> backups of /home mostly)
> so agcount should be in both cases 4, as i haven't got a raid (the 1,5
> tb disk won't be in the LVM neither).
> I have read that in xfsprogs 3.1.2, i think, -l lazy-count=1,version=2
> and -i attr=2 is the default option like agcount=4. So  i should only
> specify the -l size=128m if i want a log size of 128m for improve
> deleting performance and improving system in general.

With a single disk filesystem, you can tweak these things forever, and
you will gain almost no performance benefit over the mkfs.xfs defaults,
though you may decrease performance if you don't know exactly what
you're doing, such as with your previous misunderstanding of agcount.

The one thing you can tweak beyond defaults to get improved performance
is using delayed logging, which will increase metadata write performance
substantially.  For example, deletes of large groups (thousands) of
small files will be "massively" faster using delayed logging.  IIRC this
requires kernel 2.6.36 or later.  Simply add "delaylog" to you
/etc/fstab mount options.

> I think in /home the most important thing is read/write seqential
> performance , and in /data (the 350 GB partition) the same.
> I don't think /data would have to handle too many ramdon reads/ writes
> when Maya saves and read data from it, i think would be mostly
> seqential and then allocated in memory.

Again, with a single disk, there's not much you can tweak to increase
general XFS performance, except for metadata writes using delaylog.  For
sequential file reads/writes and random reads/writes, you're at the
mercy of the drive's spindle speed.

XFS options can't improve upon the poor physics of a single spinning
drive.  If you need improved file performance (not metadata), your
options are to add spindles and stripe the data (RAID card or mdadm,
RAID 0/5/6/10), or use a good quality SSD.


<Prev in Thread] Current Thread [Next in Thread>