I'm new to XFS and researching the use of XFS as the filesystem for an
application that writes sequential data streamed from gigabit Ethernet. This
data is then read at the fastest possible throughput for further processing.
After reviewing the mailing list archive, I am unsure of what options (both
in the app and at filesystem creation) should be used to ensure the greatest
throughput (currently estimated at 40MB/s+).
The application will be written in C++ on a Linux 2.6 system.
Is there a way to increased the buffered i/o for a file to be larger than
64K (XFS_IOC_SETBIOSIZE in man xfs(5)) or would this have minimal effect on
read/write performance? Is buffered i/o part of the delayed allocation that
I have read from other sources?
(http://www-106.ibm.com/developerworks/linux/library/l-fs9.html)
If I know the size of the data before receiving it, should I use the
XFS_IOC_RESVSP64 (man xfs(5)) in the application with unwritten=0 option set
for the filesystem? Using this technique, would it be reasonable to assume
the XFS overhead is low enough for the throughput to be near the hardware
benchmarks (sustained read/write)?
I appreciate your time answering all these questions.
Regards
Nick
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
|