On 17/08/2012 09:15, Stan Hoeppner wrote:
On 8/16/2012 2:52 AM, David Brown wrote:
For those that don't want to use XFS, or won't have balanced directories
in their filesystem, or want greater throughput of larger files (rather
than greater average throughput of multiple parallel accesses), you can
also take your 5 raid1 mirror pairs and combine them with raid0. You
should get similar scaling (the cpu does not limit raid0). For some
applications (such as mail server, /home mount, etc.), the XFS over a
linear concatenation is probably unbeatable. But for others (such as
serving large media files), a raid0 over raid1 pairs could well be
better. As always, it depends on your load - and you need to test with
realistic loads or at least realistic simulations.
Sure, a homemade RAID10 would work as it avoids the md/RAID10 single
write thread. I intentionally avoided mentioning this option for a few
reasons:
1. Anyone needing 10 SATA SSDs obviously has a parallel workload
2. Any thread will have up to 200-500MB/s available (one SSD)
with a concat, I can't see a single thread needing 4.5GB/s of B/W
If so, md/RAID isn't capable, not on COTS hardware
3. With a parallel workload requiring this many SSDs, XFS is a must
4. With a concat, mkfs.xfs is simple, no stripe aligning, etc
~$ mkfs.xfs /dev/md0
These are all good points. There is always a lot to learn from your posts.
My only concern with XFS over linear concat is that its performance
depends on the spread of allocation groups across the elements of the
concatenation (the raid1 pairs in this case), and that in turn depends
on the directory structure. (I'm sure you'll correct me if I'm wrong in
this - indeed I would /like/ to be wrong!) If you have large numbers of
top-level directories and a spread of access, then this is ideal. But
if you have very skewed access with most access within only one or two
top-level directories, then as far as I understand XFS allocation
groups, access will then be concentrated heavily on only one (or a few)
of the concat elements.
raid0 of the raid1 pairs may not be the best way to spread out access
(assuming XFS linear concat is not a good fit for the workload), but it
might still be an improvement. Perhaps a good solution would be raid0
with a very large chunk size - that make most accesses non-striped (as
you say, the user probably doesn't need striping), thus allowing more
parallel accesses, while scattering the accesses evenly across all raid1
elements?
Of course, we are still waiting to hear a bit about the OP's real load.
--
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
