On 02/04/2012 07:43, Stan Hoeppner wrote:
On 4/1/2012 5:33 AM, David Brown wrote:
For an application like this, it would probably make sense to put the
xfs log (and the mdraid bitmap file, if you are using one) on a separate
disk - perhaps a small SSD.
XFS only journals metadata changes. Thus an external journal is not
needed here as there is no metadata in the workload.
Won't there still be metadata changes as each file is closed and a new
one started, or as more space is allocated to the files being written (I
know xfs has delayed allocation and other tricks to minimise this, but
it can't be eliminated entirely). Each time the metadata or log needs
written, you'll get a big discontinuity in the writing as the disks
heads need to jump around (especially for RAID5!).
It would make sense to have a separate disk (again, SSD is logical) for
the OS and other files anyway, keeping the big array for the data.
Putting the xfs log there too would surely be a small but helpful step?
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
