After doing some testing with a 6-node Linux cluster, pvfs2fuse on
Linux performance is comparable to the PVFS built-in client. Iozone
shows the PVFS client topping out at ~100 MB/s and pvfs2fuse topping
out at ~75 MBs for large files but for small files and small record
sizes pvfs2fuse does about 30% better. We have yet to do any
analysis of pvfs2fuse performance to see where the bottlenecks are.
Hi John,
Out of curiosity, what size files are considered small and large?
Small files are less than 1M with accesses of less than 32K.
Along these lines, if its possible to make fixes to the code that
aren't darwin/apple specific, we tend to prefer that. For example,
instead of a separate aiocb struct just for darwin, we could add a
check to the configure.in for __error_code and __return_value
fields in that struct, and if they don't exist, just #ifndef them
out where they're normally used.
Actually, I think the Apple specific code changes in dbpf.h, dbpf-
bstream.c and pvfs2-xattr.c have been fixed in the latest CVS code
using the approach you suggested. The only Apple specific thing that
needs to be fixed is the "-dynamic" linker flag in configure. And
that's not really necessary, since it just gives a warning and doesnt
break the build.
Thanks for the patch. Modulo some minor changes I think this will
be a worthwhile commit. If you're interested in reporting nightly
test builds on darwin to our tinderbox build status page so that we
can keep track of commits that break on that platform, we could
help you set that up.
See: http://www.pvfs.org/pvfs2-nightly-builds/tinderbox2/PVFS2/
status.html
I dont mind doing that, but I will probably have to get a hold of a
desktop Mac since my development has been on my laptop.
John.
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
